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 a new resolved status

Yvonne_jftvbx

Hi all,

during build stage we just needed done as last status in the workflow. Now in run we want to use a new final status after done called deploy prod.

It was no problem changing all the previous issues marked done to deploy prod with bulk operation.

BUT now the reports of all sprints before are broken: In the sprint reports the issues have all kind of status apart from deploy prod and are therefore not completed. But if you open the issue navigator all these issues have the status deploy prod and the resolution done. It seems that the change hasn't been synchronized with the reports.

Can anyone help please?

Cheers

Yvonne

Accepted answers

Petter Gonçalves

Hello Yvonne,

Sorry to hear you are facing a problem. I understand that you have recently changed your done status to a different one (deploy prod) and bulk updated it in all of your issues, however, the Sprints closed before that change are displaying in done status and returning as not resolved in the Sprint Reports. Is it correct?

About this statement:

But if you open the issue navigator all these issues have the status deploy prod and the resolution done. It seems that the change hasn't been synchronized with the reports.

The Sprint report will always consider the status that the issue was added to when the Sprint was closed, not mattering which status you added posteriorly to the issue. This is an expected behavior to track what issues needed more than one sprint to be completed and properly identify in which Sprint it was completed.

In the Sprint report documentation, you can see the following sentence:

An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.

That being said, the issue will only appear as Resolved in the Sprint that it was transitioned to the last status in the board columns. Can you check if this is the case?

Also, Could you please provide us more details on how you changed the bulk operation and how the previously done issues (Issues moved from done to deploy prod) are appearing in the Sprint report?

All comments

Petter Gonçalves

Hello Yvonne,

About this statement:

But if you open the issue navigator all these issues have the status deploy prod and the resolution done. It seems that the change hasn't been synchronized with the reports.

In the Sprint report documentation, you can see the following sentence:

An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.

That being said, the issue will only appear as Resolved in the Sprint that it was transitioned to the last status in the board columns. Can you check if this is the case?

Also, Could you please provide us more details on how you changed the bulk operation and how the previously done issues (Issues moved from done to deploy prod) are appearing in the Sprint report?

Yvonne_jftvbx

Hello Petter,

thanks for reaching out.

To your questions:

It's about issues that had as last status done when the sprint was closed. In the sprint report they still are labeled done but appear as not completed instead of completed and are mixed up with those issues really not completed.

The bulk operation: project -> issues and filters -> done issues -> advanced search -> in this view over the 3dot menu I chose bulk change all XX issues.

If you open one of these issues or open the issue navigator from the reports all of them really have the status deploy prod what makes me believe the bulk operation worked.

The board and its columns are also configured correctly I think as you can see on the screenshot:

Could it be that there is a problem with the bulk opartion and the reports? I did the same last year with a way smaller project with the only difference that I changed the status manually. This projects reports look fine.

I hope these details can help.

Thanks and kind regards

Yvonne

Petter Gonçalves

Hello Yvonne,

Thank very much for your screenshot and details provided.

Now, I was able to exactly identify where your problem is happening:

You still have the Done status in your board column, however, it is not configured as the final status of your board.

An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. As you can see in the column color, the Done column is set with the blue color, meaning the status category is In progress instead of Done:

Screen Shot 2019-08-02 at 12.11.18.png

Unfortunately, it's not possible to have multiple Done columns in a single board, as mentioned in this feature request.

That being said, I recommend you to map the DONE status together with the DEPLOY PROD in the Deploy Prod column and create a different status (Maybe RESOLVED) in order to fix the problem.

Let me know if this option makes sense.

Yvonne_jftvbx

Hi Petter,

thanks for your respond and sorry for my late one. I still think the problem lies somewhere else. In our workflow Deploy Prod is the last status instead of Done.

If the status Deploy Prod is manually set all works fine and the sprint report is correct. But when I did the bulk operation setting many issues on Deploy Prod at once the sprint report didn't check it although all issues werde updated correctly and have now Deploy Prod as status. So, I guess the bug lies in the sync between status change via bulk operation and sprint report.

Can you recunstruct the problem?

Cheers

Yvonne

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

jira-software-cloud