Tracking Team Progress: Issues Created vs. Issues Resolved Per Week in Jira

[#1]

Keeping an eye on the weekly number of issues created and resolved in Jira lets Product Managers and Team Leads evaluate the team’s performance. It demonstrates the amount of work that needs to be done and the speed at which tasks are finished.

Having such data makes it possible to spot problems quickly, lead the team well, and plan each sprint efficiently. Jira comes with some tools to assist, although they might not always cover all needs.

In this article, we will discuss how to use Jira’s built-in features to keep track of weekly issues that are created and resolved. Additionally, we’ll examine the Issue History for Jira app, which enables you to track your team’s progress in greater detail.

Why Tracking Weekly Issues Progress in Jira Matters

Keeping an eye on the number of issues created and solved weekly helps you see how well the team is doing overall. If most of the issues are being added instead of being resolved, it may suggest that the team is overloaded, has unclear goals, or is encountering some blockers.

Keeping track of issue progress each week helps Product Managers and Team Leads to do the following:

• Watch how much work the team has and be sure it isn’t overloaded.
• Notice blockers as soon as possible, so they don’t get worse.
• Check the team’s progress by monitoring how many tasks have been completed and whether they are approaching deadlines.
• Plan the sprints and set goals with the help of real data.

Jira Native Features to Track Issues Created and Resolved Per Week

Created vs Resolved Chart

📊 What it shows: The chart illustrates the number of issues created and resolved during the specified time period in a project.

✅ Why it’s helpful: It quickly displays the general trend. If the “created” line is consistently above the “resolved” line, your backlog may be growing.

⚙️ How to use:

1. In the sidebar of your project, click on Reports.
2. Go to the Created vs Resolved Chart.
3. Select the period you want to look at.

The report will look like this:

❌ Limitations: You are unable to focus on specific issues or view them by team member, issue type, or the sprint they belong to. Since it lacks exporting and live dashboard updates, weekly reporting may become less flexible.

Two Dimensional Filter Statistics Gadget

📊 What it shows: Shows a table (matrix) with issues grouped by two fields. It is helpful for a quick look at weekly results, such as “Who resolved how many issues?”.

⚙️ How to use:

1. First, create and save the necessary filters. For that, go to Filters → JQL. You can create two filters: one for issues created and one for issues resolved, within the specific project and date range. For example:

project = MARKETING AND created >= "2025-06-09" AND created <= "2025-06-15"

project = MARKETING AND resolved >= "2025-05-26" AND resolved <= "2025-06-01"

2. After that, go to your Dashboard, click Add Gadget, and find Two Dimensional Filter Statistics gadget. Add it to your Dashboard.
3. In the gadget settings, select one of your filters and complete the other required fields. Using the filters in our example and choosing Assignee and Status in the settings, we got such results:

• Marketing Tasks Created (09.06-15.06):

• Marketing Tasks Resolved (09.06-15.06):

❌ Limitations: It does not present data visualizations such as graphs or charts. Only saved filters are applicable, and there is no way to export the table data. Every week, you’ll need to change the filter settings manually.

Issue History for Jira App Usage

If you want a closer look at the history of issues, the Issue History for Jira app can help you track changes that aren’t covered by Jira’s built-in reports. It is helpful for tracking the progress of issues and who made which updates.

🎯Key features of the app:

• You can view the entire history of changes to each issue, like when it was created, resolved, or updated along with changes to its status, assignee, or priority.
• You can filter by date, employee, etc., by simply setting up a custom filter, without writing JQL.
• You can export the data to use it later on your own or to send it to other colleagues.

🛠️ How it works with Jira: Even though Jira offers charts and summaries, it does not offer a full record of how issues have changed or flexible historical reports. Issue History for Jira fills this need by letting you keep track of team activity on a weekly basis.

📝 Example of possible use cases:

• Product Manager reviewing how many issues were resolved last week across different teams.
• Team Lead comparing tasks created vs. resolved to assess workflow balance during a sprint.

⚙️ How to use:

1. Install the app via Atlassian Marketplace. When the app is installed, you can find it in the Apps menu. Open Issue History for Jira from there.
2. Apply the required filters. You can select the project, choose the date range.
3. Add the custom columns in the Columns section, such as Created and Resolved.
4. Get your report. For example:

5. Export the received results to Excel or CSV for further analysis or sharing with stakeholders.

This app allows Product Managers and Team Leads to get a more accurate picture of weekly team activity without the need to use complex JQL queries.

Summing Up

Keeping track of opened and closed issues weekly allows Product Managers and Team Leads to ensure that both the project and the team are following the plan. Jira’s built-in features are useful, but they are not very flexible and may not show a lot of historical information. Teams looking for more detailed tracking and simple reporting can try to use the Issue History for Jira app.