Jira release burndown not showing forecast after 4 completed sprints

[Maria Fomina]

Hi everyone,

I’m reviewing the Jira release burndown chart for a specific Version. We already have more than four completed sprints linked to this release, but the forecast is still not displayed.

Instead, I see the message: “No forecast available yet. A forecast cannot be shown until at least 3 sprints have been completed.”

Since we’ve already completed more than the required number of sprints, I’m not sure why the jira release burndown chart is not generating the forecast.

Is there any configuration in Jira that I might be missing to include the completed sprints properly so the forecast becomes visible? Or could you recommend a good Marketplace app that provides more advanced release burndown and forecasting capabilities?

[Iryna Krutko]

Hi Maria!

The problem: Jira's native Release Burndown Chart is showing "No forecast available yet - A forecast cannot be shown until at least 3 sprints have been completed", even though more than 4 sprints have been completed for the version.

Why this happens: This is a known limitation of Jira's built-in Release Burndown report. The native chart requires that the completed sprints are directly associated with the board you're viewing and that the issues in those sprints belong to the selected version. If sprints were completed on a different board, or if the version's issues weren't part of those sprints in the expected way, Jira won't recognize them for forecasting purposes.

A more flexible alternative:
The Agile Burnup Burndown Charts app offers a Release Burndown Chart that automatically generates min/avg/max velocity forecasts based on your team's historical data.

You can select a release (version) as the data source directly, configure how many past sprints are used for the forecast, and even pull in velocity from an alternative board or project if your current source lacks sufficient history.

Useful Docs: Forecast settings | Alternative throughput data | Sprint/interval count

You can also explore this interactive Release Burndown Chart example - it's a clickable demo showing how the forecasting works in practice.

Hope this helps - feel free to follow up if you have any questions!

[Danut M [StonikByte]]

Hi @Maria Fomina,

Welcome to the Atlassian Community. 

The Release Burndown Chart report in Jira can be difficult to use and understand—I found it challenging as well. Even if you’ve completed 4 sprints, the forecast only appears when Jira has enough consistent data to calculate a reliable velocity trend...

If you’d like to try an app from the Atlassian Marketplace, our Great Gadgets app offers a Release Burndown/Burnup Chart gadget that can solve this problem for you.

The gadget can calculate progress based on issue count, story points, time estimates, or other numeric fields. It can also include subtasks and provide an ETA forecast based on velocity and scope changes.

All you need to do is configure it with a filter or JQL query that returns the issues in your release and set the release timeline.

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

Danut. 

[Marc -Devoteam-]

Hi @Maria Fomina 

Welcome to the community.

Did you go over the documentation? https://support.atlassian.com/jira-software-cloud/docs/what-is-the-release-burndown-report/ 

A current active sprint is not counted in this report, also if tickets are in a status, that is not defined on the sprint board, these issues are not counted in the chart.

Is the fix version field set to the related version on issues in the sprints?