A Kanban burnup chart offers a clear view of project progress, aids in forecasting when work will be completed, manages evolving scope, and highlights potential delivery risks early on.
Users can select one or more boards for forecasting, tailor forecast scenarios with specific target dates and velocities, and refine accuracy by enhancing historical data. It's also possible to simulate scope increases, define custom values for remaining work, and add target date markers to support detailed planning.
Although Jira doesn’t offer a built-in burnup chart for Kanban teams to monitor progress, our Agile Burnup Burndown Charts gadget provides robust and adaptable forecasting designed specifically for practical Kanban workflows and scaled agile environments.

✅ Product or Delivery Manager: I use Kanban burnup charts to build accurate delivery forecasts grounded in team velocity. With tools like multi-board forecasting, scenario adjustments, and scope growth simulations, I can set realistic stakeholder expectations, prioritize effectively, and flag delivery risks early, ensuring steady project momentum.
✅ Marketing Manager: Kanban burnup charts help me assess which features are likely to launch by specific deadlines. This insight guides campaign scheduling and supports the timely coordination of messaging, making it easier to adapt plans when potential delivery issues arise.
✅ Scrum Master: I track remaining work through burnup charts to catch signs of scope creep or changing commitments. When forecasts shift, it signals possible risks and prompts alignment discussions with product owners, keeping the team focused and scope under control.
✅ Program Manager: In scaled agile environments, I use burnup charts across several teams and projects via a unified dashboard. This comprehensive view enables me to manage dependencies, track progress, and coordinate delivery efforts across the organization efficiently.
✅ Release Train Engineer (RTE): I leverage Kanban burnup charts to oversee progress across multiple Agile Release Trains, combining team velocities for precise Program Increment forecasting. These visuals help me identify risks, align teams, and manage cross-train dependencies to meet PI goals and timelines.
Using the team’s historical weekly velocity, the Kanban burnup report generates three automated forecast lines:
These dynamic forecast lines provide a clear view of when the remaining work may be finished under varying conditions, similar to the functionality offered in our Kanban burndown chart example.
⚙️ Default settings:

By selecting multiple boards, you can merge several Kanban boards (1️⃣) into one unified forecast view. This allows you to track total scope, remaining effort immediately, and completed work (2️⃣) across various teams - ideal for cross-team collaboration and strategic delivery planning.

For advanced customization, each board allows:

This allows complete flexibility to tailor forecasts to each team's specific workflow, whether they estimate using story points, time, or any other numeric field.
Historical velocity isn’t always sufficient, especially when aiming for fixed deadlines. That’s where the custom forecast scenarios in the Kanban burnup chart gadget become essential.
This feature lets you manually set:

This feature is especially valuable when:
Rather than passively reviewing forecasts, you can actively test, model, and plan more strategically, enabling better alignment between teams and stakeholders through data-driven insights.
The accuracy of any forecast depends on the quality and relevance of the data it's based on. That’s why these settings of the Kanban burnup chart in Jira let you fine-tune how your forecast is generated:
🧮 Adjust velocity history
By modifying the Interval Count and selecting a custom date range, you can control how many past intervals (e.g., weeks) are used to calculate the minimum, maximum, and average velocities. Using more historical data can help smooth out outliers and produce a more reliable forecast, especially useful for mature teams with steady performance trends.

⚖️ Refining forecast inputs
With the advanced issue filter, you can narrow your dataset to specific issue types, epics, or releases, ensuring your forecast is based solely on relevant work.
This degree of control in the Kanban burnup chart helps eliminate misleading projections and supports planning grounded in accurate, meaningful historical trends.

Alongside custom forecast scenarios, the Kanban burnup report in Jira dashboard also lets you simulate how changes in remaining work affect delivery timelines. This capability allows you to model scope growth over time, offering a more accurate representation of real-world project dynamics.

The Remaining work growth field offers three configuration modes:
This functionality in the Kanban burnup chart gadget on your Jira dashboard helps visualize the impact of changing requirements, scope creep, or added backlog items. It enables you to stress-test your forecasts and make more informed, adaptive planning decisions.
Although the Kanban burnup report in Jira automatically calculates remaining work based on your current backlog and progress, you have the option to manually override this value. This lets you explore how changes in remaining work could impact the projected delivery timeline.

This feature is especially helpful when:
Using custom remaining work values allows you to better understand how changes in scope could affect delivery timelines, supporting more informed, flexible planning.
You can place a target line on the Kanban burnup report to highlight important dates, such as a planned completion milestone. This visual reference helps teams and stakeholders quickly assess how actual progress and forecasted timelines align with critical deadlines.

Curious about the exact data powering your Kanban burnup chart in Jira dashboard? You can easily review detailed issue lists and breakdowns by board, project, status, and more.
Clicking on any sprint interval reveals in-depth tables displaying:
This transparency helps validate the forecast and better understand delivery dynamics.

In the Kanban burnup report on the Jira dashboard, you can fully customize the data tables, choosing which columns to display (4️⃣) and selecting how the information is broken down (5️⃣). This flexible setup offers complete transparency and control over the data, enabling deeper analysis and more informed decision-making.
Additionally, you can click directly on the forecast chart area to instantly view the list of issues representing the remaining work behind the forecast, making it easy to drill down for detailed insights whenever needed.

By using different breakdown options, you can assess backlog health from multiple perspectives.
Jira lacks a built-in Kanban burnup chart with the advanced capabilities required for effective Kanban forecasting.
By contrast, our solution delivers robust customization options, supports multiple boards, provides in-depth issue breakdowns, and includes powerful scenario modeling features, giving teams the tools they need for accurate planning and progress tracking.
For a deep dive into what native Jira's burnup Chart actually show – and where they stop – see "Jira burnup chart: what it shows, where it stops, and how to go further" article.
Use these examples to recreate similar use cases on your Jira Dashboard.
Both Jira apps (plugins) showcased here come with a 30-day free trial and are completely free for teams sized up to 10 people:
The Agile Reports and Gadgets app includes Kanban burnup chart functionality, along with many other reports and charts.
A Kanban burnup chart is a visual tracking tool that shows how much work has been completed over time compared to the total planned scope for a project or sprint. It helps teams monitor progress toward their objectives and quickly identify any changes in scope. Typically, the chart features two lines - one for completed work and another for total scope, making it easy to see how close the team is to finishing all planned tasks.
Both charts track progress over time, but they present the data differently:
You can build and customize both chart types using the Broken Build – Agile Burnup Burndown Charts app for Jira.
Burnup charts in Kanban are used to track progress toward completing a time period or project. They allow teams to visualize the amount of work finished compared to the total planned scope, making it easier to:
By displaying both completed work and total scope, burnup charts offer a transparent view of whether the team is on track to achieve its goals.
Yes, the Kanban burnup chart can use any numeric Jira field as the estimation unit. Common options include:
This flexibility lets you customize the chart to fit your team’s preferred method of estimation.
The chart displays completed work (such as story points) alongside the total scope over time. As tasks are finished, the completed work line “burns up” toward the overall planned workload, making it simple to monitor progress and detect any scope changes.
Yes. Using Agile Burnup Burndown Charts by Broken Build, you can model delivery scenarios and predict completion dates based on real or custom team velocity, while factoring in scope changes.
Jira doesn’t include a built-in Kanban burnup chart, but you can easily add one using the Agile Burnup Burndown Charts app from the Marketplace.
To add the burnup chart gadget to your Jira dashboard:


