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; } } }

Why Does Burndown Show Issue Reopened When Status is Closed?

John Halbert

When looking at the burndown chart for issues in the current sprint, several issues were just closed which now increased the remaining values. The chart says the issue was reopened, when the status is closed. Why is that?

The board uses a custom workflow, and I just looked at the closed step and the linked status is closed as well. Is there something else I need to check to make sure everything is configured correctly?

Accepted answers

All comments

Jack Brickey

@John Halbert, welcome to the Community. I would start by looking at the full History of one or more of the issues to better understand the transitions. Unless Reopened is actually a status you have created it may just be telling you it was previously reopened, e.g. To Do > In Progress > Done > To Do (reopened) > Done

John Halbert

Thanks for the response. The red line for the number of issues in the sprint goes up though... shouldn't it go down if the issue is closed?

Jack Brickey

fair question. I would have to run some tests to see the behavior firsthand but my tests might not reflect your observations. However, keep in mind that the count in the chart is based on the Resolution field. You need to see what happens when an issue is reopened. The proper behavior is to have the Resolution field cleared when reopening and of course set when closed again. The question in my mind is if you reopen and issue and the resolution is cleared but the "remaining estimate" is zero what does the count do? Increase by original estimate or not increase. I don't know that I have ever tried this or at least thought to look at the burndown impact. Should be a quick test for you to better understand.

John Halbert

Thanks for responding again. I went back and transitioned one of the issues through the workflow. I noticed that when transitioning an issue from 'Closed' to 'To Do', the burndown report shows it as being moved onto the board from an unmapped status.

I have a feeling this has something to do with what's going on, but I really don't know enough to say what that means.

Just to be thorough - our board has "Waiting for Development", "Being Developed" and "Development Complete". There is also a "Done" status that's not represented on the board (hence the previous paragraph I assume). When moving a ticket from "Done" to "Waiting for Development", the issue line on the burndown report is unchanged. There's an additional event/node recorded there, but the height is unchanged. Transitioning the issue through "Being Developed" and then into "Development Complete", however, causes the issue line's height to reduce.

Thinking through it I'm guessing the burndown chart is tied to the board, not the sprint. Is that the correct way to think of it? Because the workflow is actually split across two boards, and the sprint likewise tracks across both boards. (workflow continues from "Development Complete" to "Waiting for Testing", "Being Tested", "Testing Complete", the testing statuses being mapped to a dedicated QA board.

If what I'm saying is somewhere in the right ballpark, I will say I still find it confusing why moving the ticket to an unmapped status would cause the chart to see it as being re-opened. So, maybe I'm missing something in there. I guess for now I understand that I can leave tickets in the "Development Complete" column and expect the burndown chart for that sprint to behave the way I expect. But, it would be nice to have some idea why the report behaves like that too. Do you know what else might be coming in to play here?

Samira Negm

We the same issue and it's very frustrating!

We have separated the deployment in another board but now if an issue moves to shipment in the deployment board, the burndown sees this issue as reopened

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-software

jira-software-cloud

burndown