📊 Agile Created Resolved Charts 1.1: now on the Jira project page

[#1]

Every team that ships software faces the same running question: is work arriving faster than we can finish it? A Created vs. Resolved chart answers that directly – it tracks how many work items enter a queue versus how many leave it over a given period. When the two lines diverge, something needs to change. Agile Created Resolved Charts is one option in this category – a Jira app that builds the chart from your board, project, or JQL data, with configurable rules for how arrivals and departures are counted, multiple estimation fields, and both by-period and cumulative views.

Until this release, the chart required a dashboard setup before a user could see any data. There was no way to open it directly from a project. If you were already checking velocity or burnup burndown directly from the project page, the detour for demand-vs-capacity data felt like a step backward. Four sibling charting apps in our suite already had project page access; Created vs. Resolved was the gap.

⚡ Open a project, see the chart

Agile Created Resolved Charts 1.1 puts the chart directly on the Jira project page. Open a project, pick the Agile Created Resolved Charts tab, and get the by-period or cumulative chart scoped to that project right away – no dashboard setup, no JQL prerequisite.

The full toolbar carries over from the dashboard gadget. Import and export chart configurations, export the chart itself to CSV, PNG, or PDF for reports and stakeholders, and open Chart examples from the help menu to browse real-world setups you can copy for your own team.

🔍 What the chart tells you

The core question is demand vs. capacity: for any period you pick – sprint, week, month – are we creating more work than we're resolving?

The by-period view answers that per interval. You can render it as a bar chart or a line chart – bars work well for comparing discrete sprints or weeks side by side. When the Created bar is taller than the Resolved bar for several sprints in a row, the backlog is growing, and the team is falling behind. When Resolved pulls ahead, the team is clearing inventory. Toggle percentile lines on to spot when a specific period deviates from the norm.

The cumulative view shows the same data as running totals over time. The vertical gap between the two curves is your backlog – a widening gap means scope is growing faster than delivery; a narrowing gap means you are burning down. Inflection points in the curves reveal when things started to shift, which is useful when the conversation moves from "are we on track?" to "when did we fall behind?"

Click any interval to drill down to the exact issues driving that period's count. Below the chart, the Breakdown groups results by status, issue type, or assignee – so you can see not just that demand is outpacing capacity, but where.

A delivery manager preparing for a portfolio review or a scrum master heading into sprint planning gets the answer from inside the project – without building a dashboard first.

🏁 The shortest path to "are we keeping up?"

Open a project, click the tab, read the chart. No dashboard to build, no filter to maintain, no context switch. The answer to "are we keeping up?" now lives where the work does.

👉 Evaluate Agile Created Resolved Charts on the Atlassian Marketplace

From the Broken Build team behind Agile Created Resolved Charts