I have status "Done" under column "Dev Complete" which is a prereq for status "Complete" under the column "Accepted". I have both statuses set as resolution, however, only "Complete" reflects that a story has been closed on my burndown.
Shouldn't both statuses reflect the same progress given that they are set as resolution?
Thanks for your prompt response Tom. I will be removing the 2nd last column, and moving the status under it to the last column. THis way my last column will have both statuses "Complete" and "Accepted".
I don't understand "status set as resolution". Do you mean you have filled in the resolution field when you arrive in those statues? It's good practice to ensure any issue in the "done" column has a resolution set, as the reporting makes more sense.
In the above screenshot I have the columns Dev Complete and Accepted with the "Done" and "Complete" statuses respectively. As per Tom's recommendation, I will move the "Done" status to the Accepted column. However, do I keep both "done" and "complete" statuses "set as resolution" checked?
The goal here is to have the story resolved and reflected as progress in my burndown whether the story is "Done" or "Complete"
It's not "set as resolution", it's "set resolution". That tells the workflow to set a resolution (done) when issues go into that column, and remove it when moving to a column without it.
This is a healthy thing to do, as resolved issues (with a resolution set) are treated as dealt with by most of JIRA, but it is just for reporting and display. As Tom mentioned, the charts rely on the columns, not the resolution.
Got it. I am currently in-sprint, and will need to combine the "Dev Complete" and "Accepted" columns as well as have both "done" and "complete" statuses under that column. Will this instantly update the burndown chart given that i've already marked stories as dev complete in the 2nd last column? I am a little hesitant to modify it since I am in-sprint.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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