We are wanting to track issues in a Sprint, the trouble is they don’t get closed in JIRA terms within the sprint. The workflow is as follows:-
In Sprint terms the Scrum Board is mapped as follows:-
I’d like the Sprint, when closed, to recognise the items in the right most column (they essentially have the UAT status) as DONE. Is this possible?
The reason for this is the UAT is done by a different team to the development team, often involving third-parties and other complexities so the dev teams definition of done is matched against requirements, etc, so they can move forward onto other work (if UAT fails it will result in different tasks in future Sprints).
At the moment, the Sprint seems to be only recognising tasks as Done if they are actually closed. I can't be the only one who wants valid statuses on his issue pre and post those relevant for the Sprint?
JIRA considers an issue to be ultimately CLOSED not by the issue status, but by the system field called "Resolution" if it has a value or not. The same can be said with the JIRA Agile and the "resolution" field can be automatically set in the scrum board so the issue can be considered closed.
To do this, go and "Configure" your board then open the "Columns" tab. Drag statuses between columns and you will be prompted with a checkbox named "Set Resolution", tick this if you want the resolution to be set whenever the issue is moved to this column.
The other way of doing this is to update the "workflow transition" to the UAT status and put a post-function to "update the resolution" field.
It absolutely does support it. All versions of Jira can set a resolution on a transition, since version 1.
You might be on an old version that doesn't have the flag to do it for you in the simplified workflows, but you can still add it manually.
Possibly I'm confusing two issues.
I totally agree with you closed and the resolution field. We went through that pain and we do now have a closed status which changes the resolution, etc.
Possibly, this is something different and I'm confusing the two end points.
Basically, when we complete a Sprint we want anything in the right most column of the scrum board to be recognised as 'Done' (you're right, it's possibly not closed) so they don't fall into the next Sprint!
We'll test it with the next Sprint closure, but I'm not sure it was working last time.
Hi Gabrielle If we have to set the resolution field in order for a task to be considered done in a sprint how do we handle the fact the ticket is still live post-sprint with a few additional statuses? I am assuming here if we set the resolution field it's no longer an open issue.
Please can someone provide an answer to the above thread?
I'm using JIRA Agile to manage dev but a story's lifecycle doesn't finish at the end of the sprint. It goes onto 'UAT passed' and 'Released to prod' stages (both of which are completed outside of sprint.
So how can I close the sprint in JIRA, even though the stories within aren't technically complete (i.e. resolution field value exists)
Is there a better approach for this?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot