Sprint burndown chart includes tickets with unmapped status as +1

Question

I have a workflow with dev-test-deployment (each has a separate to-do, in-progress, done status) and created a scrum board with only status related to dev part of the workflow.

The backlog and the active sprint show the correct tickets (dev-to-do, dev-in-progress, dev-done).

However, the burndown chart shows some strange behaviour. If I change a ticket from the dev-done status to the test-to-do status, which is unmapped in the dev board, the burndown goes up +1 and the ticket is counted as Reopened.

The correct behaviour in my opinion would be not to count this ticket in the burndown chart of the dev board.

I can 'force' this by putting all unmapped statusses in the right-most column of the dev board. The burndown chart is then correct, but it seriously clutters the active sprint board with tickets the dev team is no longer interested in.

Anyone knows how to handle this?

Yves van de Vijver · Answer

I figured it out myself in the end (or at least I hope so).

I created a new filter only containing the statusses I have on the development board (New -> dev-to-do -> dev-in-progress -> dev-done). I attached that filter as the saved filter to the board.

The sprint report and burndown chart now show correct figures.

I did the same for the test and deploy boards.

I also created a total board with all statusses for maintaining the backlog and doing the sprint planning.

For now, that seems to do the trick.

Yves van de Vijver · Answer

Hi Jorge,

Thank you for responding. Maybe I should explain the workflow a little more.

We have dev, test and deployment teams  which share one workflow and sprint. The workflow is as follows:

New -> dev-to-do -> dev-in-progress -> dev-done -> test-to-do -> test-in-progress -> test-done -> deploy-to-do -> deploy-in-progress -> deploy-done -> Closed

I created three separate boards for dev, test, and deployment.

On the dev board I only show New, dev-to-do, dev-in-progress, dev-done. All other statusses are in the unmapped section. Dev-done is the right-most column.

So, when I move a ticket to dev-done, the burndown goes -1, which is correct. But, when I move a ticket from dev-done to test-to-do, which is not on the dev board, the dev burndown chart shows it as +1 again. I don't want this ticket to count in the dev report any longer, because it is in a status which is not on the dev board.

So, it seems the dev burndown report has different query behind it compared to the dev active sprint.

I hope this explains the situation better.

Best regards, Yves.

Jorge_de_Carlos · Answer

Hi @Yves van de Vijver,

If I understood you correctly, your burndown chart goes up +1 when you move a ticket from [done] to [to-do], when you are reopening the ticket. I think that process wouldn't be correct. +1 should affect when you close the ticket. [in progress-done].

If you are working in a Sprint and you want to reopen the ticket, you have to take out the ticket of the Sprint, this +1 should disappear. The you have to take into again.

¿Are you sure that your workflow process is correct?

Regards!