Why Did Adding a Workflow Status Cause Scope Change

[Matthew Langwell]

I recently added a workflow status with transitions to my teams project. The status is called "In Review" and the transitions that are in the workflow regarding this are:

• "In Progress" to "Code Complete" (Pull Request created)
• "Code Complete" to "In Review" (A Code Reviewer is looking at the Pull Request)
• Pull Request declined: "In Review" to "In Progress"
• Pull Request accepted: "In Review" to "Complete"

Now whenever a Code Reviewer changes the status of an issue to "In Review" for some reason it removes the issue from our Current Sprint. Then once the Code Reviewer accepts/rejects the Pull Request and it transitions to one of the pre-existing statuses, the issue is added back into the Current Sprint.

This is showing as "Scope Change" and looks really bad for our reports. Any help is appreciated!

[Tom Lister]

Hi @Matthew Langwell 

Did you also add the new status to a column on the sprint board?

Tom

[Veera]

@Matthew Langwell ,

When the issues is removed and added from an active sprint, it shows as "Scope Change" in the Spring report.

Make sure there is no post-function to clear the Sprint field value in the workflow transition which moves the ticket to "In Review" status.