Version Workload Report retiring on 31 July, 2026 - any replacement?

[Irina Zdanovych]

Jira Version Workload Report is retiring on 31 July, 2026. Is any replacement to be introduced? Otherwise, one will have to resort to Jira issues export to Excel with a bunch of manipulations to attain the metrics that thew report used to provide...

[Mikael Sandberg · Accepted solution]

Hi @Irina Zdanovych,

Welcome to Atlassian Community!

The deprecation of the three reports has been rolled back and lozenge has been removed after feedback from customers. You can read the PM's response here, https://community.atlassian.com/forums/Jira-questions/Why-are-Version-Report-Release-Burndown-and-Epic-Burndown-being/qaa-p/3260875#M1185560

[Irina Zdanovych]

Thank you!

[James Gamble]

Hola Irina,

I couldn’t find any Atlassian announcement of a direct replacement for the Version Workload Report. As things stand, it looks like the report is being retired without a new one-for-one native report that preserves the same per-assignee workload and remaining-estimate view.

The closest built-in option is the Time Tracking Report, which still reports Original Estimate, Time Spent, and Estimated Time Remaining for a selected version. It also provides totals for the version, but it doesn’t organize the results by Assignee as the Version Workload Report does. Atlassian describes the available reports here.

You can recreate part of the old view with a saved filter, such as:

fixVersion = "Your Version" AND resolution = Unresolved

Then use that filter with dashboard gadgets such as Filter Results, Pie Chart, or Issue Statistics grouped by Assignee. That will show who owns the outstanding items, but Jira’s standard gadgets won’t total the remaining estimate for each Assignee, so it still won’t fully reproduce the retired report.

For the exact workload totals by person, exporting the filtered results or using a Marketplace reporting app may unfortunately be necessary unless Atlassian announces another option before July 31. I’d also submit feedback through Atlassian Support, since the loss of the per-assignee remaining-work calculation is the specific gap that the other native reports don’t currently fill.

Thanks,

James

EDIT: Never mind. :D The change has been rolled back.

[Mikael Sandberg]

@James Gamble the retirement has been rolled back and will not happen just yet. Atlassian is working on replacements after feedback from customers, see my post below.