It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Release Burndown - Kanban tickets assigned to Sprints

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
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you