Why are Time tracking, User Workload & Version Workload reports being retired?

Question

Wondering why these are being retired and what I can use to get the same insights?

Josh · Answer

Hi JAGE, adding to Project Commander's reply: voting on Ben Payne's thread is the one lever Atlassian named, so do that first. Meanwhile, here is how I'd rebuild each of the three natively so nothing breaks when they go:

* Time Tracking report: a filter such as project = ABC AND fixVersion = "1.4" ORDER BY Rank in list view, with the columns Σ Original Estimate, Σ Time Spent and Σ Remaining Estimate. Use the Σ versions rather than the plain fields: they include sub-task time, which is what the old report rolled up. Export to CSV if you want the % complete column back.
* User Workload: a dashboard with the Workload Pie Chart gadget on a saved filter like resolution = Unresolved AND assignee is not EMPTY, statistic type Assignee, time field Remaining Estimate.
* Version Workload: the same gadget on fixVersion = "1.4" AND resolution = Unresolved. Put a Two Dimensional Filter Statistics gadget (Assignee × Status) next to it. That one counts work items, not hours, but together they cover most of what the report showed.

The one thing none of these do (and the old reports didn't really do either) is "hours logged per person per week." worklogAuthor = someone AND worklogDate >= startOfWeek() will find the work items, but the list still shows each item's total Time Spent, not that person's hours for the week.

If that per-person weekly view is what you actually used these reports for, Aneto Hours Reports and Resource Planner builds timesheets from the Jira worklogs you already have (by person and project, filtered by JQL). It also shows capacity next to time spent, so you can see who is over-allocated for a given week.

Disclosure: I work at Aneto Software, which makes this app.

Project Commander · Answer

The only official explanation is Ben Payne's, from Atlassian, on 13 July in the thread Gor linked. These were among the six least-used legacy reports, so a retirement banner went up to see who objected, and three were kept because people did. Time Tracking, User Workload and Version Workload drew little response, so they stayed on the list. Atlassian has not posted there since. If you rely on one, say so on that thread; it is the lever Atlassian named.

Meanwhile, Time Tracking is easy to rebuild: a filter in list view with Original Estimate, Time Spent and Remaining Estimate as columns gives the same per-issue comparison, and it exports.

For User Workload, the Workload Pie Chart gadget grouped by Assignee totals remaining estimate per person. But like the report, it only gives a total: 30 hours on someone means little until you know whether they have 20 or 40 hours available this fortnight.

Disclosure: I built a Jira app called Project Commander, on the Atlassian Marketplace. It covers that gap, setting each person's outstanding work against their own capacity after leave and holidays. It does not replace Time Tracking.

Gor Greyan · Answer

Hi @JAGE

I tried to find an official explanation from Atlassian, but so far I haven't found any documentation explaining why these reports are being retired. The current support documentation still describes the reports without mentioning the deprecation, and recent Community questions about the retirement haven't received an official response yet.

You can have a look at that thread.
https://community.atlassian.com/forums/Jira-questions/Why-are-Version-Report-Release-Burndown-and-Epic-Burndown-being/qaq-p/3255262#M1185560