I don't think so... in my experience, the burndown uses the last column as the trigger. My workaround was to build a second board for burn down reporting where the last column also included the additional statuses that we considered "Done" from an engineering perspective.
example: included the UAT status in the final column for the burndown version.
Hope this helps, oh, btw we are on the cloud version so we did not have the ability to modify code. If you are server based you might have other alternatives.
Remember, there are 2 options where JIRA Agile can consider a burndown (hence a change in the burndown charts).
So depending on what you need here, you can use option 1. If you really need to use option 2, there are options in the Agile board to set resolution on any column (regardless of status).
@Gabrielle Bautista [ACP-JA] Thanks for your reply.
You mention that option 2 allows for the burndown to be affected when a resolution status is set even when the issue is not in the final column (column on the right) of a board.
How do you achieve this? E.g. I have a total of 5 columns in my scrum board, when setting a resolution in column 3 for an issue this is not reflected in the burndown. Only when an issue has a resolution status AND is in column 5 do I see the burndown change.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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