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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

588 views 6 12
Read article

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