Change Set Analysis Variant 2

The purpose of this analysis is to check the state of the change sets in one selected branch. It is not used for merging code between branches as a single branch strategy is used. Only to create a follow up note for the unfinished work.

This could be a help when for example deciding when to create a release branch. The from date should be set to be a date after the last branch was created. It will help keeping track of the changes done on the branch since the last release branch.

The result of the work with the list is published to the project wiki and used in the standup to help focus on the important tasks to close.

On the right side of the grid there is a button menu with the following functions.

In this dialog box you select the source branch, also set a date from where you wish to start the analysis. In this case it is important to know where to search from, as you only want to see the changes done on the branch since the last release branch. The from date should be set to be a date after the last branch was created. It will help keeping track of the changes done on the branch since the last release branch. It will also give you a insight in the amount of work that remains to do with the checked in code.

This function will verify all the work items referred to in a change set, use this function when you have made changes to a work item. The changes in state will be reflected in the list. The rule for what to verify is setup in the application settings.

This functions will show all the warnings in the list. A warning is issued for a work item [task] that is in a state that doesn't belong to the Completed or Removed state category in Azure DevOps.

This function will show all the work items refered to in the change set, each work item can be opend from the list.

Use this function to view the changes in the change set. This is useful if you want to see what has been done in the change set before you decide to merge it.

This will remove a change set from the list. This is useful if you have a change set that you don't want to include in the follow up note, the state is OK to merge.

This function will filter the list to only show the work items that have warnings. A warning is issued for a work item [task] that is in a state that doesn't belong to the Completed or Removed state category in Azure DevOps. The function should be used before publishing the follow up note.

This function will publish the follow up note to the project wiki. This will create a simple wiki page, the design and content of the page is controlled by templates, the templates are found in the Settings section.

The list of change sets is an hierarchical list, meaning that the change sets are grouped by the work items they are associated with. The work items are listed in the order they are found in the change sets, so the first work item in the list is the first work item found in the first change set.

The list of items is expanded by clicking on the change set, if the change set contains warnings the line in the grid will be orange. The reason for the warning is that there is an test task to complete before the code can be merged.