nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint reports broken after adding new resolved statuses

Myron Melnyk_3s0g1b

Hello,

Having changed our project workflows by adding new statuses after Done (this status defines completion for sprint reports) our previous sprint reports like burndown, velocity charts have been broken, but Burnup one looks correct.

A screenshot of new statuses is added below.

If we take a look at a sprint report, some tickets are shown as removed from the sprint but in a fact, they are not:

The board column looks:

It seems that the change hasn't been synchronized with the reports.

Can anyone help, please?

Thank you.

Cheers,

Myron

P.S. Here I found a similar problem but provided suggestions do not help in my case:

https://community.atlassian.com/t5/Jira-Software-questions/Sprint-reports-broken-after-adding-a-new-resolved-status/qaq-p/1142614

Accepted answers

Bill Sheboy

Hi @Myron Melnyk -- Welcome to the Atlassian community!

To confirm my understanding:

Your team previously used a workflow that ended with Done
Several sprints completed
Your team added more statuses, placing them in the last column on your board
And now the prior sprints' reports are incorrect

Is this what you are experiencing? If so, the other linked discussion post is indeed what is happening: JIRA reports do not appear to use the conditions of the workflow from when the sprint completed as they re-process the logs at the time you ask for the report, using the current workflow.

By adding status values, JIRA thinks you have changed the conditions. So, bulk edit of the issues may help, as the other post notes.

Note, there is a larger issue here. I understand JIRA supports multiple status values in a board column, *and* it usually leads to side effects. Pause to consider your team's full workflow, as it seems to continue after the sprint finishes. If that work can happen during the sprint, those should be separate columns on the board, for each step. If not, perhaps there is either a need for a separate release management board, or if the team should be using something other than Scrum.

Best regards,

Bill

All comments

Bill Sheboy

Hi @Myron Melnyk -- Welcome to the Atlassian community!

To confirm my understanding:

Your team previously used a workflow that ended with Done
Several sprints completed
Your team added more statuses, placing them in the last column on your board
And now the prior sprints' reports are incorrect

By adding status values, JIRA thinks you have changed the conditions. So, bulk edit of the issues may help, as the other post notes.

Best regards,

Bill

Myron Melnyk_3s0g1b

Hi @William Sheboy ,

Thank you a lot for your replay.

1. To confirm your understanding, yes, the four mentioned points are correct.

What I found out more that is a lot of tickets from my previous sprints were moved from the statuses "UAT" and "Ready for release" to "Done" (I do not understand how it has happened). But the workflow was ... Done->UAT->Ready for Release->Released (Closed) and changed to ... Done->UAT->Ready for Release->Released (Closed). We added a new status like "Ready for testing" and changed all statuses after "Done" to a green category.

Also, it can be a reason that tickets with status "Done" are shown like removed from the sprint are not counted in sprint statistics.

image 1.png

2. Please clarify how bulk edit of the issues may help. You mean to changes statuses from "Done" to "UAT" or even "Ready for release" (all of them I can say should be in Ready for release".

Thank you.

Best regards,

Myron

Bill Sheboy

Hi Myron,

For bulk edit, I believe the other post was suggesting updating the old item status values to work-around the reporting issue. As an alternative, you could just leave those alone, remembering what the values previously were, and move forward from there.

Best regards,

Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software