This guide aims to provide an understanding of the Created vs. Resolved Report, along with a comparison to Jira's standard reporting functionality.

Overview

The "Created vs Resolved" report is a valuable metric in software development and project management. This report provides insights into the rate at which issues are being created and resolved over a specific period.

The main purpose of the "Created vs Resolved" report is to visualize the balance between incoming issues (created) and resolved issues within a given timeframe. By comparing the number of issues created with the number of issues resolved, teams can gain a better understanding of their work progress, efficiency, and workload distribution.

Here's how to interpret the report

1. Timeframe: The report typically displays data over a defined period, such as daily, weekly, or monthly. This allows you to track the trend of issue creation and resolution over time.

2. Created Issues: This represents the number of new issues that have been reported or added during the selected timeframe. It indicates the rate at which new work is coming into the system.

3. Resolved Issues: This represents the number of issues that have been resolved, fixed, or closed during the selected timeframe. It shows the rate at which the team is addressing and completing work.

4. Bar Chart or Line chart: The report is usually presented as a bar chart or line chart, with the x-axis representing the timeframe (e.g., days, weeks), and the y-axis representing the number of issues. The bar for created issues and resolved issues are plotted separately, allowing you to visually compare their trends.

Open

Report example

What this report allow users to measure?

The "Created vs Resolved" report allows users to measure several key aspects of their software development or issue tracking process. These measurements include:

1. Workload Distribution: The report helps users assess the balance between incoming work (created issues) and completed work (resolved issues). By comparing the number of issues created with the number of issues resolved, users can gauge how the workload is distributed over time. This measurement provides insights into whether the team is able to handle the volume of incoming work effectively.

2. Efficiency and Productivity: The report enables users to measure the efficiency and productivity of their team. By analyzing the rate at which issues are resolved relative to the rate at which they are created, users can assess how quickly the team is able to address and close issues. A higher resolution rate indicates improved efficiency and productivity, while a lower rate may suggest potential bottlenecks or areas for improvement.

3. Work Progress and Cycle Time: Users can measure the progress of their work by tracking the trend of created and resolved issues over time. This allows them to understand the pace at which work is being completed and identify any variations or patterns. By analyzing the cycle time (the time it takes to resolve an issue), users can gain insights into the speed and responsiveness of their team in addressing and resolving issues.

4. Team Performance: The report provides a measure of the team's performance in terms of issue resolution. Users can track and compare the number of issues resolved by individual team members or different teams within the organization. This measurement helps identify top performers, potential areas for skill development, and ensures accountability within the team.

5. Trend Analysis: By monitoring the trends in created and resolved issues over time, users can identify patterns, seasonality, or shifts in the team's performance. This allows for proactive planning, resource allocation, and process improvements based on historical data.

The "Created vs Resolved" report serves as a visual representation of the team's productivity and workload dynamics, allowing stakeholders to make informed decisions, optimize resource allocation, and track progress towards project goals.

What is missed in standard Jira "Created vs Resolved" report?

The standard Jira "Created vs Resolved" report provides valuable information about the rate at which issues are being created and resolved within a specific timeframe. However, there are a few limitations or aspects that might be considered less useful depending on the specific needs of the users:

1. Lack of Details: The standard report typically displays data on a daily, weekly, or monthly basis. While this can provide an overview of the trend, it may not offer enough details level for investigation of every particular case.

Standard Jira "Created vs Resolved" report	Jira Service Management Data Series report built against Created vs Resolved dates	Actonic’s Report Builder "Created vs Resolved" report

Standard Jira "Created vs Resolved" report	Jira Service Management Data Series report built against Created vs Resolved dates	Actonic’s Report Builder "Created vs Resolved" report
Open

1. Limited Filtering and Customization: The standard report may not offer extensive filtering options or customization capabilities, which can limit its usefulness for specific analysis needs or for teams with unique workflows.

1. One additional limitation of the standard Jira "Created vs Resolved" report is the lack of export functionality. While the report provides valuable insights within the Jira platform, there is no built-in capability to export the data for further analysis or sharing with stakeholders outside of Jira.

To overcome these limitations and gain more comprehensive insights, users may consider using Report Builder app. This plugin can provide more advanced metrics, customizability, and drill-down capabilities to meet specific reporting requirements and provide a more comprehensive view of issue creation and resolution dynamics.