"Created vs Resolved" report inflates the Created count — appears to calculate Created as 2×Resolved

Yigit Yoleri

Product: Jira Cloud

Component: Reports — Created vs Resolved

Summary: "Created vs Resolved" report inflates the Created count — appears to calculate Created as 2×Resolved + Unresolved instead of Resolved + Unresolved

Description:

The "Created vs Resolved" chart in Jira Cloud project reports is displaying incorrect values for the "Created" line. The Created count appears to be calculated as approximately 2 × Resolved + Unresolved rather than the correct Resolved + Unresolved.

Steps to Reproduce:

1. Navigate to a project's Reports → Created vs Resolved

2. Set the period to Weekly and the range to 270 days

3. Compare the Created values shown in the chart against manual JQL counts for the same weekly periods

Expected Behavior:
The Created count for any given period should equal the number of issues with created dates falling within that period — i.e., Resolved + Unresolved issues created in that window.

Actual Behavior:
The Created line is significantly inflated. For example, for the week of Dec 8, 2025:

• Chart shows: ~158 Created

• Actual (via JQL): 98 Created (project = RMDP AND created >= "2025-12-08" AND created < "2025-12-15")

• Resolved that week (via JQL): 60 (project = RMDP AND resolved >= "2025-12-08" AND resolved < "2025-12-15")

• Observed formula: 2 × 60 + 38 ≈ 158 — matches the inflated chart value

This pattern holds consistently across all weekly periods in the report.

Verification Method:
Independent JQL count queries were run for each weekly bucket across the full 270-day range. Totals: 1,190 created / 1,131 resolved. The chart's Created totals are roughly double the actual figures.

Impact:
This makes the Created vs Resolved report unreliable for tracking backlog growth, team throughput, and issue intake trends. Teams relying on this report for sprint planning or capacity analysis will draw incorrect conclusions.

James Gamble

Hola Yigit,

I'd be a little careful with the formula you're using to validate the chart.

The Created and Resolved lines are not two halves of the same weekly bucket. Created is based on when the issue was created. Resolved is based on when the Resolution field was set. So the 60 issues resolved during the week of Dec. 8 may include those created weeks or months earlier. They don't necessarily belong inside the 98 issues created that same week.

Because of that, this check can give you a misleading result: Created = Resolved + Unresolved.

That only works if the Resolved and Unresolved numbers are both limited to issues created in that same week.

I'd test the Dec. 8 week this way instead:

Created that week: project = RMDP AND created >= "2025-12-08" AND created < "2025-12-15"

Created that week and currently resolved: project = RMDP AND created >= "2025-12-08" AND created < "2025-12-15" AND resolution IS NOT EMPTY

Created that week and still unresolved: project = RMDP AND created >= "2025-12-08" AND created < "2025-12-15" AND resolution IS EMPTY

The last two should add up to the Created count for that week.

The Resolution field is still worth checking, but mostly for the Resolved line. Jira treats an issue as resolved when the Resolution field has a value, not just because the status is Done. Atlassian covers that here: https://support.atlassian.com/jira/kb/best-practices-on-using-the-resolution-field-in-jira-cloud/

Also, make sure no one added a Resolution value named "Unresolved." In Jira, unresolved means the Resolution field is empty. If "Unresolved" exists as an actual resolution value, Jira will treat those issues as resolved.

I'd also check the report settings before assuming the chart is wrong. Make sure cumulative totals aren't enabled, that the report uses the same project or filter as your JQL, that subtasks are included or excluded the same way, and that the weekly buckets line up with your site's time zone.

I'd probably capture one clean example with the report settings, the chart tooltip for the week, and the matching JQL counts above. That should make it easier to tell whether this is a date-bucket/filter mismatch, a Resolution configuration issue, or an actual report bug.

Thanks,

James