What is the trigger that makes a sprint believe that an issue is "Done"? In the past, on our old server version, I thought this was determined by the "Resolution" field. In the new cloud version I am using, it seems like the only way I can get the sprint to recognize an issue is done is to have it put in the "Closed" status. The problem I have with this, is I have a test phase after our development phase, but I want to close the sprint after things are moved to the QA phase. Is there a way to set the "determining factor" of what a sprint counts as a "done" issue sp I can close the sprint without the tickets being pushed to the next sprint?
Hi @Jason Huntowski,
Sprints are a feature of a board. And although both status and resolution both have a clear relation to what people consider 'done', for a sprint board this is just everything that is in the rightmost column of your board.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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