We configured our workflow so that we have have a status of Deployed (for code that has been successfully tested and deployed). This status is mapped to a category of Done in the status definition screen. We also have status of a Closed in the workflow, for issues that are resolved for other than deployed status. This status is also mapped to a category of Done.
The problem that we're having is that when we set the status for an issue to Deployed, we're expecting these issues to drop off when we create a new sprint since these issues were resolved from the previews sprint.
How do we get this to work?
Make sure "closed in the workflow" and "deployed" are included in the last column.
It seems there's more to this than that. Our rightmost column is just called "Done" and issues marked as "Done" are moving to the next sprint. (We have it set so that there are different resolution options when moving an issue to the right most column, but that only affects the "Resolution" field which you said doesn't matter).
When issues have incomplete sub-tasks we get an error and can't even attempt to close the sprint. ("Sprint cannot be completed as there are incomplete subtasks on the following issues...")
But you pointed me in the right direction. It was the opposite; there were a couple of large parent tasks in the verify column who had all of their subtasks in done. Thanks!
Create two (or more) Boards: First board is your current board with columns for all steps of the workflow showing. This is for the team's day to day issue management. Create a second board with all 'Resolved' issue statuses (i.e. Deployed and Closed) in the last column. Use the Second board specifically for closing sprints. This will ensure story points for all resolved issues are accounted for in velocity and sprint reports, while having the other board to show all statuses clearly.
We have the same set up and problem. Last two columns of the board are for issues that are 'Done'. When moving issues into 2nd to last workflow step, the resolution screen comes up and tickets are marked with a resolution (i.e. Done, Won't Do, Cannot Reproduce, etc.). There is no change in Resolution status when moving into the last workflow step.
When I click Complete sprint on the Active Sprint page, I would expect all issues with a Resolution (i.e. Done) would drop from the sprint, but they roll over to the next sprint. This causes Done issues to be in the new sprint and not credit these Done tickets to the velocity.
We don't want to put two states in the last column because we lose visibility of this status and cannot drag between columns.
The solution is as follows:
Once you move them to this status, they will disappear from the board, but as they are technically mapped to the far right column, they won't be carried forward to the next sprint :-)
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events