Created vs Resolved chart in Jira Dashboard

Q: What is a Created vs Resolved chart in Jira?

A Created vs Resolved chart visualizes how work enters (created) and leaves (resolved) your system over time. It helps teams compare incoming demand with completed work to understand if they are keeping up or building a backlog.

Q: What is the difference between Resolved and Done in Jira?

Resolved indicates an outcome has been recorded (the 'why' it is finished, e.g., Fixed, Duplicate), while Done is a workflow status indicating the current stage of the process (the 'where' it is).

Q: How do you interpret a Created vs Resolved chart?

In the 'By Period' view, you compare demand vs capacity per sprint. In the 'Cumulative' view, a widening gap between the lines indicates a growing backlog, while a narrowing gap shows the team is catching up.

Q: Who will benefit from using Agile Created vs Resolved Charts?

Scrum Masters, Product Owners, and Team Leads benefit at the team level. Delivery Managers and Program Managers benefit at the cross-team level, while Portfolio Managers and Executives gain high-level visibility into delivery health.

Q: How do you calculate Created vs Resolved in Jira?

It is calculated by tracking issues based on their creation dates versus the date they reach a resolution state. Tools like Agile Created Resolved Charts allow you to customize these events based on specific statuses or transitions.

Q: Can I visualize cross-team Created vs Resolved data in one chart?

Yes. The app supports aggregating data from multiple boards, projects, releases, and custom JQL filters to visualize system-wide flow in a single chart.

Q: How do I add a Created vs Resolved chart to a Jira dashboard?

Install the Agile Created Resolved Charts app, then add the 'Created vs Resolved by Broken Build' gadget from your Jira dashboard's gadget library.

Q: How much does the Agile Created Resolved Charts app cost?

The app is free for teams with up to 10 users. For larger teams, pricing scales by user count. A 30-day free trial is available for all users.

Key features of Agile Created Resolved Charts in Jira

Track created vs resolved issues across one or multiple boards, projects, releases, and portfolio levels - from epics to initiatives - or refine the scope with JQL filters.

Analyse created vs resolved issues over flexible time ranges and group results by day, week, sprint, or month to adapt to your team’s reporting approach.

Set estimation fields, define defaults, and control how created and resolved work is counted - based on your workflow.

Track total created vs resolved work over time to understand system stability and backlog dynamics.

See if backlog is growing, stable, or shrinking
Compare cumulative demand vs delivery
Identify long-term trends, flow stability, and delivery gaps
Spot scope creep or sustained improvement

Understand how much work enters and leaves your system in each time interval. Compare Created and Resolved side by side to detect imbalances, variability, and emerging risks early.

Choose which metrics to display to better understand demand vs delivery dynamics.

Show or hide Created (Arrived) and Resolved metrics
Enable average lines (mean, median, or moving average) to assess delivery stability

Focus only on relevant work to ensure accurate insights and cleaner analytics.

Refine your chart scope to match your workflow by filtering issues using Issue types, Epics, Releases, or custom JQL.
Exclude outliers, test tasks, or irrelevant issues from calculations.

Break down demand and delivery by team, assignee, issue type, release, JQL, or any Jira field to understand what drives created vs resolved trends. Drill down to the issue list to validate the exact work items behind the metrics.

Adjust your Created vs Resolved chart settings with a what-you-see-is-what-you-get editor - define arrival & completion events, apply filters, and see results update instantly, without extra clicks or reloads.

Export Created vs Resolved charts in CSV, PNG, or PDF formats, and export chart settings to quickly reuse, share, or standardize reporting across teams.

Frequently Asked Questions

1. What is a Created vs Resolved chart in Jira?

A Created vs Resolved chart in Jira visualizes how work enters (created issues) and leaves (resolved issues) your system over time. It helps teams compare incoming demand with completed work to understand whether they are keeping up, building backlog, or improving flow.

This type of chart is essential for identifying bottlenecks, tracking delivery performance, and maintaining a healthy balance between demand and capacity.

With apps like Agile Created Resolved Charts for Jira, you can go further - customise how events are counted, analyse trends by period or cumulatively, apply advanced filters, and drill down to the exact issues behind the data.

2. What is the difference between Resolved and Done in Jira?

In Jira, Resolved indicates that a resolution has been set for an issue, meaning the work is considered completed from a tracking perspective. It reflects that the issue reached an outcome (e.g., fixed, won’t do, duplicate).

Done, on the other hand, is a workflow status that shows where the issue currently sits in the process. An issue can be moved to Done without a proper resolution, depending on how workflows are configured.

In short:

Resolved = outcome recorded (why it’s finished)
Done = workflow stage (where it is)

For accurate reporting, both should be aligned - especially when analyzing delivery metrics like Created vs Resolved.

3. How do you interpret a Created vs Resolved chart?

The Created vs Resolved chart by Broken Build shows how work flows through your system - from incoming demand (Created) to completed work (Resolved). You can read it in two main views:

By period (run) view

Compare Created vs Resolved per sprint or time bucket
If Created consistently exceeds Resolved, demand is outpacing capacity, and backlog will grow
If Resolved is flat or dropping, it may indicate bottlenecks or delivery issues
Use breakdown and drill-down to identify where inflow or outflow changes (by team, issue type, etc.)

Cumulative view

Tracks total Created vs Resolved over time
The gap between the lines represents backlog or WIP
A widening gap means the backlog is growing
A narrowing gap means the team is catching up
Sudden changes in curve shape can signal risks or shifts in delivery pace

Together, these views help you balance demand and capacity, detect bottlenecks early, and forecast delivery risks based on real flow trends.

4. Who will benefit from using Agile Created vs Resolved Charts?

Created vs Resolved charts are valuable for teams and leaders who need visibility into demand, delivery, and flow across different levels of the organization.

Team level

Scrum Masters - monitor flow stability and remove bottlenecks
Product Owners - understand backlog growth and prioritize effectively
Agile Team Leads - balance demand and team capacity

Cross-team level

Delivery Managers - track performance across multiple teams
Program Managers - identify systemic flow issues and dependencies
Release Train Engineers - ensure smooth delivery across ARTs
System Architects / Solution Managers - align delivery with system constraints

Organization level

Portfolio Managers - oversee the delivery health and investment flow
C-level Executives - get high-level visibility into delivery performance

Agile transformation

Agile Coaches - guide teams using flow-based metrics and continuous improvement

With Agile Created Resolved Charts in Jira, each role can go deeper - from high-level trends to issue-level insights - using flexible filters, customizable calculations, and drill-down analytics.

5. How do you calculate Created vs Resolved in Jira?

Created vs Resolved is calculated by tracking the number of work items that enter the system (Created) and leave the system (Resolved) within a defined time period, such as a day, week, or sprint. Created typically reflects issue creation dates, while Resolved is based on when issues reach a completion state (e.g., Done, Closed, or a custom resolution event).

Teams can also customise how these events are counted - for example, defining specific statuses, transitions, or resolution fields that better reflect their workflow.

Tools like Agile Created Resolved Charts by Broken Build aggregate these events directly from Jira workflows, allowing you to configure arrival and completion logic, choose time intervals, and analyse trends in both per-period and cumulative views.

6. Can I visualize cross-team Created vs Resolved data in one chart?

Yes. Agile Created Resolved Charts in Jira support cross-team analysis by aggregating data from multiple sources, including boards (Scrum/Kanban), project scopes (projects or releases), issue hierarchies, epics, and custom JQL filters.

This allows you to compare how work is created and completed across multiple teams, projects, or workflows in a single chart, helping you spot imbalances between demand and delivery, identify bottlenecks, and understand system-wide flow.

7. How do I add a Created vs Resolved chart to a Jira dashboard?

To add a Created vs Resolved chart to a Jira dashboard, install the Agile Created Resolved Charts app and start with a free 30-day trial. After installation, open your Jira dashboard, go to the gadget library, and add the Created vs Resolved gadget by Broken Build.

The chart will appear instantly, allowing you to track how work enters and leaves your system, monitor demand vs delivery trends, and analyze flow directly in Jira.

8. How much does the Agile Created Resolved Charts app cost?

The Agile Created Resolved Charts app is free for teams with up to 10 users. For larger teams, pricing scales by user count and can be calculated here. A 30-day free trial is available, so you can explore all chart features and flow analytics before making a decision.

Agile Created Resolved Charts

Transform Created vs Resolved data into clear, actionable delivery insights

From data to delivery clarity with the Created vs Resolved chart in Jira

Real-time created vs resolved visibility

Beginner-friendly. Powerful when you need it.

One bundle. Complete delivery visibility.

Take control of keeping up with demand

Key features of Agile Created Resolved Charts in Jira

Frequently Asked Questions

Related interactive Examples

Cumulative Created vs Resolved chart

Why trust Broken Build apps?