Hi, I have a workflow of the form:
open->in progress->in test ->complete
As far as my development team is concerned, the work is done when items enter the 'in test' status, since the UAT and merge to production happens outside the sprint.
Ideally I'd like:
The burndown chart to show issues in test as counting towards sprint progress (set to resolved, not closed)
I need to keep the 'closed' status for items that have completed UAT.
I can't seem to get Greenhopper reports to identify these tickets as counting towards completion, so the burndown always looks hardly worked on, and in order to make it correct, when the sprint finishes I need to temporarily drag the status of 'in test' into the final Done column in the board configuration settings.
Actually the way how burndown chart works is to burn the values base on the last column in the columns mapping in your board configurations.
So my suggestion is to set 'In Test' in the last column then you can set 'Closed' before 'In Test' or you can merge those together. I know that might not make some logical sense but that's how GH works indeed.
Ah, ok, makes sense, but quite annoying from a useability point of view, since we have some ticket types that need to go through UAT, and others that can bypass this and go straight from 'in progress' into complete.. Getting my developers to understand and use a back-to-front column set-up would be tricky.
Thanks for your explanation for how it's being implemented though.. it would be nice to have this as a config setting, so Greenhopper boards can be configured to show resolved or closed tickets in the burndown (rather than always having it as tickets in the final column).
As far as I can see, there is still no appropriate answer to the initial question. Now, 5 years later: Is there a way to display more than just the one "Done" graph on the board?
My User Story: As a Scrum Master I would like to see a graphs for "in progress" and "in test", so I can challange the team to have less work in progress.
We have the same issue, our scrum teams are "done" once code is pushed to production queue, but we cannot close the tickets until the code is actually live in production. Having a burndown chart based on "closed" status have been messing up all of our team's sprint reports.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs