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?

[Marita Burgio]

Hi @Maria Fomina

As others mentioned, Jira's native Release Burndown has limitations with forecast generation.

eazyBI Reports and Charts for Jira offers a flexible alternative for release burndown and burnup reporting with forecasting capabilities:

• Create custom burndown/burnup charts based on Fix Version, Story Points, or time estimates
• Add velocity-based forecast lines using historical sprint data
• Combine data from multiple sprints and projects
• Customize the forecast calculation logic to fit your team's needs

You can check demo reports for forecast and management here: https://eazybi.com/accounts/1000/dashboards/16201-forecast-and-management

You can build reports similar to sprint burndowns but filtered by Fix Version to track release progress. eazyBI includes sample reports for sprint burndown that can be adapted for release tracking.

The app is available on the Atlassian Marketplace with a free trial.

Feel free to reach out to support@eazybi.com if you need help setting up release burndown reports.

Best,

Marita from support@eazybi.com

[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?