Created vs resolved
Navigation |
|---|
Report Usage
This report comes in the form of a line chart report. It represents a created issues trend and resolved issues trend for the chosen current period. On the Y-axis user can see the number of issues. On the X-axis user can see the Start and End date.
Specific functionality:
On the report card, we can additionally add the Unresolved trend line. It shows the trend between created and resolved tasks.
Labels can be added and removed. While they are added the user can see the number of tasks created or resolved at a certain period.
When hovering the label tooltip appears. It shows the selected date, and ratio of created issues to resolved issues on this day and by this day.
Under the name of the report, the user can see the number of Issues created and Issues resolved for chosen days.
To review all tickets Created or Resolved on a certain date, open a sub-table by clicking on a label. For full guidance on how to work with subtables, see the Working with Subtables .
If the labels are positioned one above the other, clicking on them will display a pop-up with options.
Setting up a report
The report has 5 tabs of configurations: Data source, Parameters, Display, Subtable, Description.
Data source
This report supports filtering issues by Basic Source, Saved Filter, or JQL query. For full guidance on how to configure your data source and , see the Data Source & Report Description
Specific Report Parameters
Period determines the time unit by which the data will be grouped and shown as labels on the line. The default value for this field is Days.
When the period is set to "Day" or when the period is set to "All Time" and the data spans only one day, the data will be broken down hourly. This provides more granular visibility into issue creation and resolution patterns within a single day.
When the period is set to "All Time" and the project contains data spanning multiple days, the breakdown periods are automatically determined based on the volume of data in the project:
For projects with limited data (few days to weeks), data may be grouped by days
For projects with moderate data (weeks to months), data may be grouped by weeks
For projects with extensive data (months to years), data may be grouped by months
This automatic period determination ensures optimal chart readability and performance regardless of the project's data volume and time span.
Display
In this tab, the user can configure visual elements of the report:
Show unresolved trend toggle - enables or disables the unresolved trend line on the chart. When enabled, this line shows the difference between created and resolved issues, providing insight into the backlog growth or reduction over time.
Show Label toggle - controls the visibility of data point markers (dots) on the trend lines. When enabled (default), dots appear at each period interval on the lines. When disabled, only the trend lines are visible, though data point information will still be accessible on hover.
Show aggregate issues toggle - enables or disables the display of aggregated issue counts. When enabled, the chart shows cumulative totals of created and resolved issues over time, providing a running total view. When disabled, the chart displays only the count of issues for each specific period interval.
Report Use Cases
✅ Evaluate if the team is delivering features as fast as new ones are requested or scoped.
✅ Show how quickly bugs are being addressed over time.
✅ Monitor hourly patterns of issue creation and resolution during critical periods (when using daily breakdown).
✅ Analyze long-term trends across different time scales automatically adjusted based on project data volume.