This question is in reference to Atlassian Documentation: How do Story Points get burnt down and reflected on the Burndown Chart
Is it possible to change which column is 'done' for the burndown chart?
We use 'approved by team' which is the one I would like to use for the burndown chart to see if we're on schedule. After that there are two more columns 'approved by testing' and 'approved by client'.
Now the burndown uses the last column as a reference. Can I change this?
It will always be the last column. But you can map the statuses you want to that last column.
Ideally, a board is for a team and only the statuses that applies to that team should be mapped on the board. And in that case, the last column will be the status 'defined as done' by that team!
It is still the case, basically Jira takes the last column as the end of the process always.
Our use case is that we want clients to approve tasks during sprint review, so we had 4 columns: To do, In Progress, Done, Accepted.
Since Sprint review is every 2 weeks, the burn down looked like we did all the work on the last day of the sprint.
We decided to revert to 3 columns (remove Accepted) and use Labels to mark tasks as accepted by the client.
Not sure this will help, but it's a work around for this particular case.
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
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