Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sprint Report Unable to use StatusCategory to Burn down work Edited

We are using a sprint board and our sprint report is only able to use the last column of the board which we have as, "Accepted" (where our PO accepts the work). We also have a column, "Done" for when the dev team has completed the work. The sprint report does not burn down work when in either column, only when it is in the last column. Why doesn't the sprint report allow for status category = done as the flag to burn down work?

1 answer

0 votes

Because Jira Software only looks at the last column on a board to see if something is "done".  Status Category is not the last column on the board (although it is worth matching it up so that it is), it's a categorisation of a status, which might not actually be accurate (frankly, I've yet to see a Jira where the admins have got it completely right throughout when we start the "fix this" projects)

I know. The question I have is, why does jira software only look at the last column on the sprint board to flag completed work? I am aware of what StatusCategory means, and I agree, I can't think of a scenario where Atlassian has gotten it correct. They seem novices in the area of empirical process control, and it's as if they aren't capable of knowing how to implement an application life-cycle management tool. Maybe they should have stuck to bug tracking? At any rate, we are using this solution. Still don't know why, as it's a cash cow and bleeding us dry. Over 6K / month with all the plug-ins etc. we are using. Not worth the spend, imho. So Atlassian, can you make StatusCategory = "done" flag the sprint burndown/burnup as complete? Thank you. What do I need to do to get this implemented? Completed work can be something other than the last column on the board, as done = "potentially ship-able" and accepted means Product Owner accepts the work and ready to ship. Help!

Like Leonardo Bagella likes this

same problem. it's more useful to track all the Sprint until the very end basing the burn down/up progression on the "Completed" category more then a single status. I want the burn down report goes down when my stories are tested, not when they are approved by PO (last step) otherwise the graph is completely useless. Or shouold I change my process beacuse the tool doesn't allow that ? (unaccettable). Please consider the idea to change this behaviour.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

870 views 2 22
Read article

Community Events

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

Events near you