Jul 08, 2019 - 04:08 AM
Dirty Flag is a background service and thus user has to cofigure it on xml files( For details of configuration, please refer to attached document "Dirty Flag Technote.docx"). As soon as the defined conditions met on TFS / Azure DevOps, background service will execute and mark the defined target work item as dirty. A tag is added on target work item displaying source work item information i.e. work item id and revision id, also further details are added in Discussion field of target work item.
Lets take an example, please consider a scenario for configuration that when a User Story work item is changed associated Test case work item should be marked dirty.
Now its pre state are defined as when User Story work item is in state of “Active”, “Resolved” or “Closed” and any user make any changes to defined fields(fields are also cofigurable) i.e. In Description field, State field or Title; then mark associated Test case as dirty. (Configuration of above case is shown in attached image "DF example.jpg" )
Please refer to video link shared below, in which this scenario is executed and shown how associated Test Case is marked dirty. I hope this will clear your understanding and working of Dirty Flag.
In case of any further assistance required, feel free to contact us.
Thanks and Regards,