Why isn't my Sprint burndown report burning down for team-managed projects?

[Henry Min]

I'm using a team-managed project and utilizing the sprint burndown report. However, I've noticed that the red line in the report only reflects the total story points remaining in the sprint and moves downward only when a story is moved to the "done" status. My workflow consists of a start-to-finish process with significant milestones in between. I'm wondering if there is a way to make the red line burn down based on the start-to-finish steps in my workflow, rather than solely relying on story points. Currently, my team doesn't revise story points on a daily basis. I appreciate any advice you can provide.

[Joe Pitt · Accepted solution]

Beware of deleting production issues. Deleted is DELETED. There are tons of people looking for ways to bring back deleted issues. Basically you can't.  If you have a backup you can restore to a different instance and then export to csv and import the deleted issues.  I have a resolution value of Deleted I use to close issues we would want to delete. 

JIRA will not reuse issue numbers.  

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You can delete issues if you have the necessary permissions. It is set up at the project level, using permission schemes.

See https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html for more details.

[Alexey Matveev · Accepted solution]

Hello,

You should grant to your user the Delete Issues permission in the project permission scheme.

[Steffen Paul]

Thanks for your help!

[Alexey Matveev]

You are welcome! If any of our answers helped you, kindly accept these answers. You can accept all three answers or two answers or a single answer, if you feel so. In this case users with a similair question will be able to find accepted by you answers.