The interactive chart is available on larger screens
Please open this page on a desktop to try it out
Key features of Epic burndown chart
The Epic burndown chart gives you a clear view of progress toward completing one or more epics, while providing flexible forecasting tools to plan ahead.
You can compare multiple delivery scenarios, refine how forecasts are calculated, and add milestone markers to track against release dates.
Epic burndown graph with forecast based on last 3 intervals in Jira
The Epic burndown chart is part of the Agile Burnup Burndown Charts app. You can place it directly on your Jira dashboard (like any other Broken Build gadget) and tailor it with flexible filters and breakdown options to align with your team’s workflow.
How different roles use Epic burndown chart
✅ Program Manager: I need to forecast completion for strategic epics tied to a Program Increment so I can adjust priorities and communicate realistic delivery dates to stakeholders.
✅ Release Train Engineer (RTE): I want to track multiple epics in one view to spot risks, manage dependencies, and keep the Agile Release Train aligned with PI objectives.
✅ Scrum Master: I use the chart to monitor whether sprint-level progress supports epic completion goals and to facilitate discussions when timelines are slipping.
✅ System Architect: I need to confirm that enabler epics are progressing on schedule so dependent feature work won’t be blocked in future increments.
Keep epic delivery on track with the EPIC BURNDOWN CHART
The Epic burndown chart goes beyond Jira’s native report, which relies solely on an average past velocity. It automatically generates three projections using your team’s minimum, average, and maximum delivery pace, allowing you to compare optimistic, realistic, and conservative outcomes at a glance.
Multiple forecasting views in the Epic burndown report in the Jira dashboard
For even more control, you can model custom scenarios:
Enter a target velocity to see the expected completion date (1️⃣)
Set a fixed date to calculate the pace needed to meet it (2️⃣)
Use a velocity percentile from historical data for more conservative or optimistic projections (3️⃣)
Run a Monte Carlo simulation to see the probability of completing the work by different dates (4️⃣)
Custom Epic burndown scenarios modeling on Jira Dashboard
✅ When to use it:
Evaluating whether your current pace is enough to hit upcoming deadlines
Preparing alternative delivery plans in case scope increases or velocity drops
Comparing best- and worst-case timelines to guide stakeholder expectations
2. Key feature: Forecast inputs refinement
The Epic burndown chart lets you choose exactly how the forecast is built. You can define thenumber of past intervals that should influence the projection and add a scope growth factor.
Forecast inputs refinement settings in Epic burndown chart example
📊 How to read the chart:
The Epic burndown chart example above shows the total scope and completed work over the last six bi-weeks (1️⃣). Forecasts are calculated using the velocity from the past three bi-weeks (2️⃣), with an assumed scope increase of five issues per bi-week (3️⃣).
✅ When to use it:
Modeling delivery timelines when you know scope will keep growing
Testing how far back in history gives the most reliable forecast
Adapting projections for teams with changing workloads or seasonal peaks
3. Key feature: Multiple epic selection
With the Epic burndown graph, you can track progress across several epics in one view. Choose epics directly from a list or apply a custom JQL filter to include exactly the ones you need.
Multiple epic selection in the Epic burndown report in Jira
✅ When to use it:
Tracking related epics that contribute to the same initiative or release
Building a consolidated delivery view for stakeholder updates
Including all workstreams tied to a high-priority business objective in a single forecast.
4. Key feature: Targets visualization
Add one or more target deadlines directly to the Epic burndown chart to see how your forecasted completion dates align with planned milestones:
Targets visualization settings in the Epic burndown report
✅ When to use it:
Checking if the current progress supports hitting release or milestone dates
Communicating timeline expectations to stakeholders in a clear visual format
Prioritizing work when deadlines for multiple epics overlap
5. Key feature: Remaining work breakdown
Click anywhere in the forecast area (1️⃣) to drill down into the epic’s remaining work. You can group the issues by release, issue type, project, or other fields to see how the outstanding scope is distributed (2️⃣). Clicking the row takes you directly to the issue list linked to Jira tickets (3️⃣) for further review or action.
Remaining work breakdown example in the Epic burndown chart gadget
✅ When to use it:
Understanding how the remaining work is split across releases, teams, or work types.
Spotting high-impact areas that may delay the epic’s completion.
Quickly navigate to the underlying Jira issues for follow-up or reassignment.
Additional feature: Export
You can export the Epic burndown chart in CSV, PNG, or PDF format for deeper analysis outside Jira, or to share a snapshot of the chart with stakeholders or include it in reports and presentations:
Epic burndown chart in Jira export options
✅ When to use it:
Analyzing chart data in spreadsheets or BI tools (CSV export)
Sharing visual snapshots with stakeholders in presentations or reports (PNG/PDF)
Keeping a record of progress at specific project milestones
What about the native Jira Epic burndown chart
Jira’s built-in Epic burndown report can give you a basic sense of progress, but it’s not designed for advanced forecasting or multi-epic tracking. It only generates a forecast if the epic spans three or more active sprints, and it doesn’t allow you to model custom scenarios or fine-tune the data behind the projection.
You also can’t:
❌ View multiple epics in the same chart.
❌ Break down progress into remaining work vs scope changes.
❌ Configure estimation fields, Done statuses, or reporting intervals.
❌ Add the chart as a gadget to your Jira dashboard.
❌ Filter by individual team members to see personal contributions.
Advantages of using the Epic burndown chart
Compare optimistic, realistic, and conservative delivery timelines, or create your own “what-if” scenarios.
Choose the exact historical period for forecasts and factor in expected scope growth.
Track several epics at once, even across different teams or projects.
Overlay target dates to instantly spot risks to delivery commitments.
Filter by assignee, component, or custom JQL for more granular insights.
Export to CSV for analysis or PNG/PDF for stakeholder communication.
The Agile reports and Gadgets app includes Epic burndown functionality plus a wide range of additional charts and reports.
Frequently Asked Questions
1. How to create an Epic burndown chart with custom forecasting?
Jira’s native Epic burndown doesn’t support custom forecasting, but the Agile Burnup Burndown Charts app by Broken Build does. Simply choose the Epic Burndown (Forecast based on last 3 intervals, Scope change, and Completed work) template, select the relevant epics as your data source, and adjust the settings to match your needs.
2. How is the forecast in the Epic burndown graph calculated?
The Epic burndown chart calculates forecasts using your team’s historical delivery pace (velocity) over a selected number of past intervals, such as sprints, weeks, or bi-weeks. By default, it generates three projections based on the minimum, average, and maximum velocities from that period.
You can refine the forecast by adjusting the lookback window or adding a scope growth factor, and you can also create custom “what-if” scenarios to model different target dates or velocities.
3. How do I add multiple epics to a single Epic burndown chart in Jira?
Go to the Data source section and either select the epics from the list or use a custom JQL filter to include exactly the ones you need:
4. Can the Epic burndown graph in Jira track progress without sprints?
Yes. You can choose to display the chart by days, weeks, bi-weeks, months, or quarters, and group the data accordingly: