Release Burndown - Kanban tickets assigned to Sprints

Sarah January 20, 2020

Hello,

I find tickets in my Release Burndown Report which are assigned to no Sprints. Is this a common problem?

Here an example: 

I select a specific Version (e.g. SW_3.0) for the Release Burndown. Then I see all the Sprints where this Version (e.g. SW_3.0) is entered. And for each Sprint I have a list of all tickets. When I have a closer look to one Sprint, I see that sometimes there are tickets with no Sprint assigned. They are from a Kanban Board. And also in the history of the ticket, no Sprint is mentioned.

So, why is this ticket then here in the Release Burndown, in the list of a specific Sprint?

0 answers

Suggest an answer

Log in or Sign up to answer