What are some best practices for generating clean burn down charts?

We want to be able to do a better job tracking my team's velocity per sprint, but our sprints often include stories tied to epics that span across multiple sprints.  What's the easiest way to make sure that burndown charts reflect only work that is tied to specific sprints?

1 answer

I am not sure what you mean. The burndown chart only shows the work in the single sprint you selected. Can you elaborate?

Thanks for your feedback. I was asking for a friend. Apparently, they were having issues with stories not being accepted that was causing issues. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,878 views 12 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot