Multiple done states - Sprint Report not accurate anymore

Alexandru Armean August 30, 2018

We configured our workflow to have multiple done states ("development done","done", "released").

The sprint report only accounts in the burn-down chart and the "Completed Issues" only issues with the state "released" are displayed. All issues from states "development done" and "done" are displayed in the "Issues Not Completed".

Is there any solution to fix the sprint report to count all tickets from done states?

 

 

2 answers

1 accepted

2 votes
Answer accepted
Ryan Fish
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 30, 2018

@Alexandru Armean

JIRA burndown is based on the status associated with last column in board configuration. You can assign multiple statuses ("development done","done", "released") so burndown occurs as you desire.

 

Hope this is helpful

Alexandru Armean August 30, 2018

thanks a lot, yes indeed, by moving all the done states in the last column the sprint report is accurate again.

 

Although... we now lost the functionality to track progress between the different done states :( , but i will figure another solution for that.

Ryan Fish
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 30, 2018

yeah, thats an unfortunate consequence of lumping them into one column.

Try using a query like: status changed from status1 to status2

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 30, 2018

Did you put all the "done" status in the LAST column on the board?

Alexandru Armean August 30, 2018

no, i did not, thanks for the hint, this was indeed the issue.

Suggest an answer

Log in or Sign up to answer