Not all of my Sprints are showing in my Release burndown Report

[Tina Strother]

I am attempting to run the Release Burndown Report. I have 5 sprints within this Release. When running the report, it shows the correct start and end dates of 14/Oct/25, 12/Jan/26. However, the report is only showing the original estimate at start of version and Sprint 5. There is no information being provided for Sprints 1-4.

According to this page, I should be able to see the information needed, if nothing more than everything showing as completed at this time. I am looking to find similar information that is provided on the Epic Burndown Report ie:

• Story points at the start of the Sprint
• Points added to Epic
• Points completed within the Sprint
• Points remaining at end of Sprint

I have ensured all my issues have the fix/version, Sprints were opened/closed, all tasks are in done status, all issues have story points. I am unsure of what may be causing the issue of only showing one Sprint in the Release Burndown Report.

Any assistance would be greatly appreciated!

Thank you in advance,

Tina

[Iryna Krutko_Broken Build]

Hi @Tina Strother ,

The issue you're describing - where Jira's native Release Burndown Report only shows the start-of-version estimate and the last sprint, skipping Sprints 1–4 — is a known limitation of the built-in report. It often fails to display per-sprint breakdowns correctly, especially when sprints were closed retroactively or when issues weren't linked to the version at the time each sprint was active.

What you're looking for — story points at the start of each sprint, points added, points completed within the sprint, and points remaining at the end — is exactly the kind of sprint-by-sprint release tracking that Agile Burnup Burndown Charts provides. Using a release as the data source, the chart plots remaining work, completed work, total scope, and scope changes across every sprint in the version. You can click on any sprint interval to see a detailed breakdown of completed work and scope changes for that specific sprint, giving you full visibility into how the release evolved over time.

The app also includes automatic velocity-based forecasting (min/avg/max) so you can project when remaining release work will be done. It's free forever for teams of up to 10 users.

Documentation:
• Using releases as a data source
• Burndown chart
• Breakdown & issue list

Interactive example: Release Burndown Chart — this is a clickable demo showing exactly how the chart works with release data.

Marketplace: Agile Burnup Burndown Charts

Feel free to reach out if you have any questions about the setup — happy to help!

[Danut M _StonikByte_]

Hi @Tina Strother,

Welcome to the Atlassian Community.

The Jira Release Burndown Report can be challenging to use effectively. For better release tracking, it may be worth exploring apps on the Atlassian Marketplace that offer more flexible charts or reports.

If you’re open to trying an app, I recommend taking a look at the Release Burndown Burnup Chart gadget provided by our Great Gadgets app.

This gadget is easy to use and more flexible than the built-in Release Burndown Report:

1. It uses a filter or JQL query as its data source, so you can simply configure it with a JQL that returns all issues included in your release.
2. It does not rely on sprint data; instead, you can configure the timeline and align it with your sprints as needed.
3. Supports calculations based on any estimation field, such as story points, issue count, time estimates, or a numeric custom field.
4. Can include subtasks in the calculations
5. Can track scope changes over time
6. Can provide forecast predictions based on team velocity.
7. Can display milestones
8. The data is displayed as a line chart, in line with agile methodology.
9. Can be configured as a burnup chart

See more details here: https://community.atlassian.com/forums/App-Central-articles/9-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Danut.

[Tina Strother]

Hi @Danut M _StonikByte_ 

I am unable to add any gadgets as I am in a hosted environment. 

Thank you for your suggestion,

Tina

[Marc -Devoteam-]

Hi @Tina Strother 

Welcome to the community.

Are all the issues on every sprint add to the release?

Has the affect version field been used.

Are issue carried over from sprint to sprint.

Is a "Done" status in the last column of your scum board, as I don't see any burned items in your report in comparison to the example you provided.

[Tina Strother]

Hi @Marc -Devoteam- 

Thank you for your quick reply.

To answer your questions:

• Yes, all issues in every sprint have been added to the release.
• No, affect/version was not used.
• Yes, there were a handful of stories that rolled from sprint 1 to sprint 3 but only a few, all others were completed within the sprints they were committed to.
• Yes, done status is in the last column of my scrum board. This is a release that has been released as it ended Jan 12. I am thinking I should see how many story points were at the beginning of the release, then move throughout the release over the 5 sprints showing how many were completed per sprint and how many are left for the release.

*Something I just noticed, I went into my jira plans to check the number of stories which rolled. Only sprint 5 is showing in my plans. It seems as though I have lost sprint 1-4 somehow. If I use a jql, I can search for those stories/tasks within those sprints and find all my issues. So my issue is not that I am using the release burndown incorrectly, but jira is not seeing my sprints. Any thoughts on this?

[Marc -Devoteam-]

Hi @Tina Strother 

What is the JQL that you are using as the source of your plan?

[Tina Strother]

The JQL is project = <name> AND Sprint in ("<sprint 1>", "<sprint 2>", etc)

I am able to see all 38 issues that were planned for the 5 sprints. I can simplify the JQL to only show sprints 1 and/or 2 and see only those issues. 

[Marc -Devoteam-]

Hi @Tina Strother 

So if you JQL, project = <name> and sprint = "<sprint 3>", there is no result?

Can you provide a screenshot of the release an all the issues in the release, is the completed?

[Tina Strother]

No, I apologize for any confusion. I can make the JQL inquiring sprint 1, 2, 3, 4 and/or 5 and see the issues within the inquired sprint(s), whether I have one or more sprints in the JQL. I have no problem seeing the issues or the sprints except in Jira Plans and the Release Burndown chart. 

This is obviously a me issue lol.

[Marc -Devoteam-]

Hi @Tina Strother 

Are all sprints closed, and are all issues in the same project otherwise I can't think of any reason why the report is not working as expected.

You could reach out the Atlassian Support, please keep me in the loop on their suggestions and or solution

[Tina Strother]

Yes, all sprints are closed and also in same project.

Thank you for your time in looking into this with me. I will let you know what I find out.