Jira Is Retiring the Time Tracking, User Workload, and Version Workload Reports: What to Use Instead
If you've recently opened the Reports section in Jira, you may have noticed something concerning.
Several native reports, Time Tracking Report, User Workload Report, and Version Workload Report, will be retired. The reports were originally scheduled to be retired on July 31, 2026, but Atlassian postponed the retirement until August 30, 2026.
While Atlassian has announced the retirement, it hasn't yet provided a direct replacement for these reports. If your team relies on them to estimate remaining work, balance workloads, or plan releases, you may be wondering what comes next.
Let's take a look at what these reports were used for and how you can replace them.
Why were these reports important?
Although they were relatively simple, these reports answered questions that many project managers, team leads, and scrum masters ask every day:
-
Are we spending more time than originally estimated?
-
How much work is still left?
-
Who is overloaded?
-
Which team members own the remaining tasks?
So despite their simplicity, these reports provided valuable insights that helped teams plan work, balance workloads, and keep projects on track.
Will Atlassian replace them?
It's difficult to say.
Some of these reporting capabilities can already be reproduced using Atlassian Analytics, but that requires Jira Premium or Enterprise and often involves creating custom queries and dashboards.
Atlassian may also introduce new dashboard reports in the future, but at the time of writing there has been no announcement of a direct replacement for these three reports.
So if you're using Jira Standard, or simply want more flexible reporting, you'll likely need another solution.
What's One Alternative for Those Reports?
Rather than looking for a one-to-one replacement for each report, consider this an opportunity to rethink how you report on project data in Jira.
Instead of opening multiple reports, the Jira dashboards let you bring all the information together in a single place. You can combine issue-level details, workload summaries, release information, and project KPIs on one screen, making it easier to monitor your projects without constantly switching between different reports.
Another advantage of the Jira dashboards is flexibility. Built-in reports have fixed layouts and predefined fields, while dashboard gadgets can usually be configured to display the data that's most relevant to your team. As your reporting needs evolve, you can update the dashboard instead of adapting your workflow to fit a predefined report.
Here's one approach that has worked well for our customers well before those reports were retiring.
Build One Dashboard Instead of Three Reports
Having all this information on one dashboard makes it much easier to monitor project health. Instead of navigating between different report pages, you can see issue details, team workload, release readiness, and project metrics together in one place.
Recreating the Time Tracking Report
The Time Tracking Report was mainly used to compare Original Estimate, Time Spent, and Remaining Estimate for project issues.
For example, a similar view can be easily recreated by using the Work Breakdown Structure (WBS) gadget offered by Great Gadgets app. Configure it to display those same fields and you'll have an issue-level report very similar to the retiring Jira report.
The advantage is that you're not limited to those three columns. You can also include fields such as Assignee, Fix Version, Sprint, Priority, Status, or any other Jira field that's useful for your team. Instead of seeing only time tracking information, you get additional context that helps explain where the work belongs and who is responsible for it.
Recreating the User Workload Report
The User Workload Report showed the remaining estimated work assigned to a user.
One limitation of the built-in report was that it displayed one user at a time, making it difficult to compare workloads across the entire team.
With a Pivot Table & Pivot Chart gadget like the one offered by Great Gadgets app, configured to split data by Assignee and/or Project and sum-up the Remaining Estimate field you can get a much clearer overview that allows comparing every team member's workload in a single table and quickly identify who may be overloaded or who has capacity for additional work.
You can also split the workload by Project, Issue Type, Sprint, Fix Version, or other Jira fields to better understand where each person's work is coming from.
If you prefer a visual overview, the same data can be displayed as a heatmap or different chart types, making workload imbalances easy to spot during planning sessions.
Recreating the Version Workload Report
The Version Workload Report focused on the remaining work for a single version.
Using a Pivot Table & Pivot Chart gadget like the one from Great Gadgets app, you can recreate this view by filtering the issues for one or more versions and grouping the data by Fix Version and Assignee while summing the Remaining Estimate.
One improvement over the retiring report is that you aren't limited to viewing a single version. By adding pivot tables configured with each Fix Version, you can compare workloads across multiple releases in the same dashboard.
If you need to see the individual issues of each user behind those numbers, you can use the Work Breakdown Structure (WBS) gadget to display issue-level details such as the summary, assignee, issue type, and remaining estimate, exactly as the Jira Version Workload Report did. Or, if you want to make the report more interesting, the WBS lets you add additional fields to better understand each workload. For example, you could also add and visualize the status of each issue assigned to a specific user.
Complete Your Dashboard with Custom Metrics and KPIs
Recreating the retiring reports is a great first step, but it's also an opportunity to improve the way your team tracks projects.
Instead of relying on a few static reports, you can build a dashboard that combines detailed issue information, workload summaries, release insights, and custom KPIs in a single place. This gives project managers, Scrum Masters, and team leads a complete view of their projects without constantly switching between different reports or dashboard tabs.
One gadget that works particularly well alongside the Work Breakdown Structure (WBS) and the Pivot Table & Pivot Chart gadegts is the Advanced Issue Filter Formula gadget.
The gadget lets you calculate and display custom metrics directly on your dashboard, making the most important project information visible at a glance. Rather than searching through tables for key numbers, you can surface them as KPI tiles at the top of the dashboard.
So instead of opening three separate Jira reports, you get a single dashboard that brings together everything you need to monitor project progress, balance workloads, and track releases. And because each gadget is fully configurable, your dashboard can evolve with your team's reporting needs instead of being limited to the fixed functionality of built-in reports.
If you'd like to see how these gadgets work in practice, you can explore Great Gadgets for Jira with a free trial and start building reports tailored to your own projects and workflows.
👉 Try Great Gadgets free on the Atlassian Marketplace:
Was this helpful?
Thanks!
Danut M _StonikByte_
3 comments