nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why are Version Report, Release Burndown, and Epic Burndown being retired?

patrick_10lfjd

All 3 reports I regularly use. The most frustrating part about all of this is that there is seemingly no alternative being added as a replacement. Not a better version, not the same version, but simply nothing.

If there truly are going to be replacements/alternatives, I would love to be made aware of this, as I will end up needing to create all 3 of these reports myself.

Is there a reason as to why it is being retired? What are you all going to use instead? Screenshot 2026-06-30 at 3.51.20 PM.png

Accepted answers

Ben Payne_seo7q5

Hi all, thanks @Darryl Lee for bringing this post to my attention.

Firstly thank you for the feedback, without you raising this and commenting we'd be operating in the blue!

Why the retirement banners?
We were looking through old reports that have minimal usage. The ones listed for retirement were among the bottom six. We placed a banner to see if we'd get feedback from the community outlining their importance (as usage doesn't always reflect importance).

Because of your feedback we'll not retire these reports:

Version report
Epic burndown
Release burndown

As for the other reports Time Tracking, User Workload, and Version Workload we've received minimal feedback around the usefulness of these reports so will still schedule them for deprecation unless we hear more from users and the community.

What's the future intent?

In the future we're looking to retire our legacy reports and allow you to rebuild them inside of space insights. This will not only be more performant, but it will also offer you far better sharing and analysis features as we can power analysis with Rovo and your Teamwork graph to uncover trends you might have missed before. We've been using this internally at Atlassian and it's made an impact on our teams.

Reading this thread there's a few major things we need to address before moving reports across

JQL scoped insights so we have parity with reports that respect a boards JQL filter (this is something we're currently looking into)
Build our widgets in a way where a general burndown / burnup / report is available across different object types, i.e. epic, sprint, version etc. (something we're also looking into now)

Apologies for the shock, in the future I'll be sure to post a community article accompanying the change to ensure you're all aware.

Please leave any further questions and feedback in this thread and I'll get to it.

Thanks again,

Ben

All comments

Jason Krewson

I was unaware of this and it's sad to see them go, I remember using Epic Burndown in the past of the last company I worked for though I never used the other two.

Hopefully someone is aware of what's going on with these and will share here.

Otherwise you could always give feedback in the app on this.

bruce chalupsky

We rely on these charts to communicate with Stakeholders what delivery date to expect. I'm going to bookmark this forum to see what they have in mind- if anything.

Honestly if this is just to drive purchasing another an add-on... >;-(

Darryl Lee

Hi all!

tl;dr - I don't know for sure, but I think it has to do with a new Space Insights feature.

So I happened to remember covering a new Dashboard something or another that is coming to Bundled Release Tracks next month (and apparently is hitting Standard sites and those not on Release Tracks now), and totally thought this had something to do with that:

Space Insights: Customizable dashboards

Notably it says:

4. To find existing reports like burndown or velocity charts, select the more reports button at the top left of the view.

But yeah, on my Enterprise Test Site I have the exact same screen as after going to the Reports tab and clicking [More reports].

I'll note that the "new" Reports are in a modal, instead of the old Reports tab. So I checked my Free Test Site that usually gets things later, and I also have RETIRING lozenges for three completely different reports — Time Tracking, User Workload, and Version Workload:

I was going to ask you to click the links next to the lozenges, but ugh, apparently they are FEEDBACK LINKS. Lame.

Oh, we've got some feedback all right. :-P

Selecting one of those reports, I get this very unhelpful banner:

I can't help but think that this has something to do with the new Space Insights thing. They have a whole video about it on their new Seasonal Jira Releases (🎅?) website at https://jira.launchnotes.io/:

All your team’s metrics, one smart space

Because it is a Loom video, I am adding a comment for @Ben Payne asking if he knows anything about the deprecation of old Reports. (Hi Ben!)

I'll keep digging around for what's up with the Reports deprecations....

[Thanks to @Trudy P Claspill for lighting up the bat signal.]

Danut M _StonikByte_

Hi @patrick

Indeed, it does appear that these project reports are being retired, and it's not yet clear whether they will be replaced with something equivalent. Some of this reporting functionality may eventually be implemented through Analytics, but that's a Premium/Enterprise feature.

In the meantime, another option is to look for an app (add-on) on the Atlassian Marketplace that provides the reports or diagrams you need.

If you're considering using an app, one possible alternative is the Release Burndown Burnup Chart gadget included in our Great Gadgets app. It provides advanced reporting capabilities and may be a good replacement for these reports, depending on your needs.

The gadget can track cross-team releases, versions, or epics, it can forecast ETA based on velocity, allows displaying milestones, and is highly configurable.

For any questions, feel free to contact us at support@stonikbyte.com.

Danut.

Darryl Lee

Comment on Loom added here:

https://www.loom.com/share/c1919b0e34214b388f168606d862488c?highlightComment=00000000-0a85-8000-8000-00000000bdd5&t=108

Hi Ben - so speaking of the old Reports - we've noticed many old reports tagged as RETIRING JUL 31, 2026. Is this related to the new Space Insights reports?

https://community.atlassian.com/forums/Jira-questions/Why-are-Version-Report-Release-Burndown-and-Epic-Burndown-being/qaq-p/3255262

Reports listed as retiring in "new" Reports tab: Version Report, Release Burndown, Epic Burndown

Reports listed as retiring in "old" Reports tab: Time Tracking, User Workload, and Version WorkloadThanks!

Edwin Stol_vp8wch

Will be replaced by these:

https://support.atlassian.com/platform-experiences/docs/participate-in-the-home-dashboards-early-access-program/

Darryl Lee

Really @Edwin Stol? Because I'm reading that this "EAP gives you access to the dashboards beta in Atlassian Home"

What is Atlassian Home?

So that's this:

(Which I think is what you see at https://home.atlassian.com/)

I've just turned this on for my test site:

And from this description, they sound targeted at individuals and teams, NOT projects:

Home dashboards are for individuals and teams to find and resume work and understand the progress of their work across the Atlassian apps on a particular site. They offer flexible reporting with a wide set of data points and don’t require technical expertise to configure. Home dashboards are available to paid plans (availability to free plans coming around mid-2025).

Ah, here's what it looks like:

I created dashboards using each of the templates, and got these:

Editing those Dashboards, I see many of the same Widgets and Templates as on the new Reports Dashboards, and it looks like you can do some sharing of Dashboards:

This is interesting though, and really does lead me to believe these are NOT your regular Jira reports or dashboards:

Q: Can I use JQL saved filters or Jira boards to populate data for my dashboard?

Home dashboards don’t support using JQL saved filters or Jira boards to refine your data.

As Home dashboards supports data from across all your Atlassian tools, we support a general set of dashboard filters that allow you to drill-down across all of your app data.

Edwin Stol_vp8wch

@Darryl Lee My previous reaction was a bit short (being on the phone and all).
I think that the current 'stale' reports (that are system-defined) will be superseded by this kind of dashboarding and reporting functionality. First step is home, second step are the agile reports. Again, this is my prediction, this was not formally confirmed in any shape or form afaik..

bruce chalupsky

> Stares out window

> Takes long drag on a cigarette

> I don't even smoke

> *sighs

> "Called it."

Gaetan Massot

Is it possible to extend the availability of the Version Report beyond July 31, 2026?

As of now, we are not aware of any equivalent alternative within Jira that provides the same level of information.

This report is critical in our project to know whether we are on track or not on the current fixVersion (Release).

Trudy P Claspill

Hello @Gaetan Massot

You would need to contact Atlassian about that.

You could try the Feedback option shown in the images from @Darryl Lee

Gaetan Massot

Thanks! I did at the bgeniing of the week as soon as I noticed this pop up but was not contacted until now

Tatiana_kiqnqg

Hey Patrick! 👋

The short honest answer: Atlassian hasn't published a clear "this replaces that" for these three, which is exactly why the banner feels so abrupt. From what's been pieced together so far, they're part of a bigger move away from the old system-defined board reports toward the new Home/Space dashboards — the deprecation notes literally point you to the "more reports" button instead of naming a real successor.

A few things worth knowing while you plan around it:

• It's not just these three — Time Tracking, User Workload and Version Workload are on the same retirement list, so it's a batch cleanup of the legacy reports, not a targeted removal.

• The new Home/Space dashboards are the intended direction, but right now they don't support JQL saved filters or board-scoped data, so for release/version tracking they're not a 1:1 replacement yet. If that's a hard requirement for you (sounds like it is for your fixVersion tracking), that's the exact gap to raise.

• The most useful thing you can do is leave that feedback through the in-app "Give feedback" option on the retirement banner itself — that's the channel the product team actually reads, and version/release forecasting is a strong case to make while the decision is still in motion.

If you need coverage before July 31 and the native path isn't ready, the Marketplace does have release/version burndown and forecasting gadgets that rebuild these specific charts — worth a look purely as a stopgap.

Hope that at least clears up the "why" — you're not missing an obvious replacement, it genuinely isn't fully there yet.

Gaetan Massot

Hi all,

I have noticed this morning that the banner disappeared.

Could it be that the reports will remain after July 31?

Thank you all for your help and have a nice week.

Ben Payne_seo7q5

Hi all, thanks @Darryl Lee for bringing this post to my attention.

Firstly thank you for the feedback, without you raising this and commenting we'd be operating in the blue!

Because of your feedback we'll not retire these reports:

Version report
Epic burndown
Release burndown

What's the future intent?

Reading this thread there's a few major things we need to address before moving reports across

JQL scoped insights so we have parity with reports that respect a boards JQL filter (this is something we're currently looking into)
Build our widgets in a way where a general burndown / burnup / report is available across different object types, i.e. epic, sprint, version etc. (something we're also looking into now)

Apologies for the shock, in the future I'll be sure to post a community article accompanying the change to ensure you're all aware.

Please leave any further questions and feedback in this thread and I'll get to it.

Thanks again,

Ben

Darryl Lee

Thanks for responding to my various pings, @Ben Payne .

I think if you were looking to gather feedback on potential deprecations, could I suggest that the wording be adjusted accordingly?

None of these lozenges or banners like they're asking for input, but rather an abrupt announcement:

I don't know how flexible the UI is, but maybe next time instead of a feedback form, you link to yeah, a Community Article would be a fine place to gather input.

At any rate, appreciate you joining us here.

Ben Payne_seo7q5

The UI is constrained, but completely agree we should also link out to a community post to accompany the feedback form.

Thanks again for reaching out

Lalaina Haja

Hi @Ben Payne,

Thanks for the clarification.

I have two questions regarding the Time Tracking Report, as our users currently rely on it quite heavily.

- Is there a confirmed retirement date for the Time Tracking Report? We previously saw an in-product notification indicating it would be retired, but the notification has since disappeared.

- Can Space Insights currently reproduce the same functionality, particularly the comparison between Original Estimate and Time Spent (estimate accuracy), or is there another recommended replacement?

We're currently assessing replacement options, so any guidance would be greatly appreciated.

Thanks!

Hempel

Good questions − both are worth a direct answer.

On the Time Tracking Report retirement date: based on current community discussions and Atlassian's communications, there's no confirmed date yet. The in-product notification disappearing is consistent with what others have seen − Atlassian sometimes shows early deprecation notices and then adjusts timelines. I'd recommend watching the Jira Cloud changelog and raising it with your Atlassian rep if you need timeline certainty.

On replacing the Original Estimate vs Time Spent comparison: Space Insights focuses more on issue and sprint metrics than detailed time tracking variance. For the specific workflow of comparing Original Estimate, Time Spent, and Variance at the issue level − especially with date-range filtering − Tempo Time Tracker has a dedicated Time Tracking Report that does exactly this. It shows Original Estimate, Est. Time Remaining, Time Spent, Variance (calculated as Original Estimate − (Time Spent + Est. Remaining)), and a progress bar per issue.

Element	What is it?	What can I do with it?
A	Previous and Next icons	Click to scroll to the previous or next week.
B	Time display dropdown	Select to display the day, week, or month.
C	Worked Hours dropdown	Select to display the daily, weekly, or monthly worked hours.
D	Original Estimate column	Displays the initial estimated time specified in the issue field.
E	Est. Time Remaining column	Displays the current estimation in the Estimate field. It is reduced when work is logged on an issue, and may be increased if there is more work needed.
F	Time Spent column	Displays the sum of worklogs for an issue, during the period selected. Note, there is also a Jira issue Time spent field, which is the overall value of time logged for an issue.
G	Variance column	Displays the time variance, calculated as Original Estimate - Estimate (Time Spent + Est. Time Remaining).
H	Original Estimate Remaining column	Displays the calculation of Original Estimate - Time Spent.
I	Progress Column	Displays a progress bar for a quick visual cue of the progress per issue. Calculated as Time Spent / ( Est. Time Remaining + Time Spent). Displays as 100% when Est. Time Remaining is 0.
J	Total row	Displays the total time per time column, as well as the total progress for the displayed table.

Worth evaluating if estimate accuracy is something your team tracks closely.

Disclosure: I work for the team behind Tempo.

Nuno Araújo_9nc2cs

We would like to flag active, ongoing usage of the Time Tracking Report and User Workload Report within our Infrastructure & Operations (I&O) project category, and ask that their scheduled deprecation on July 31, 2026 be reconsidered — the same way Version Report, Epic Burndown, and Release Burndown were.

Over the past 12 months, this category alone has 1,381 issues with logged worklogs and 1,626 issues with time-tracking data (original estimate / time spent), spread across 17+ active projects — mostly network infrastructure rollouts at multiple dealership sites, plus a dedicated internal support/services project. At least 10 team members across these projects rely on time-tracking data for capacity and estimate tracking.

None of the current native alternatives (dashboard gadgets, filters, Atlassian Analytics) reproduce the per-assignee workload and remaining-estimate totals these two reports provide out of the box — removing them would force manual exports or a paid Marketplace app for a workflow that today works natively.

We'd appreciate these two reports being reconsidered with the same weight given to the other three, and ask that any future deprecation be accompanied by a native replacement preserving per-assignee time-tracking and workload reporting.

James Clark _ TribusIT

hi @Ben Payne Adding a data point on the Time Tracking Report, as it sounds like feedback is what decides this one.

I'm an Atlassian Solutions Partner and I've just started a discovery with a new customer who uses it as part of a documented commercial process. It's not casual usage. Their support desk runs a subscription setup where the time summary from that report gets pulled into the subscription record, and it's how the wider team sees how many hours a customer has left against pre-paid consultancy. Take the report away and a step in their standard operating procedure stops working.

I'd guess that's part of why the usage numbers look low. It's a small number of people running it regularly against a lot of customers, rather than lots of people running it occasionally. Low volume, high consequence.

Two things would help:

Is there a confirmed retirement date? A few of us have seen the in-product notice appear and then disappear, so it's genuinely unclear whether 31 July still stands. Hard to plan a replacement against a date nobody's sure of.

Would you consider Time Tracking alongside the three you've reversed? Or if it is going, what's the recommended replacement for the Original Estimate versus Time Spent comparison? Space Insights was mentioned, but I've not seen confirmation it can reproduce that today.

On the banner itself, I'd echo what others have said. It reads as a decision that's already been made rather than a request for input, so I suspect plenty of affected users saw it, assumed it was settled and didn't comment. That would skew the feedback you got. Worth bearing in mind when you're reading the low response as low importance.

Thanks for engaging on the thread, it's appreciated.

James

Dan Breyen

I'm agreeing with everyone here saying these reports should hang around.

We're just getting into using Jira for Time Tracking, Project Planning, and Capacity Planning. From what I say, these reports, especially the "Time Tracking" one will be very useful in this endeavor. From what I saw, the only alternatives would be to use some sort of third party app.

It's a challenge when users are forced to get third party apps because Atlassian is removing functionality.

vasanth_tka9pi

Also, can tempo time sheets reports like time report sheet will it replace?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

version

release

fix-version

release-management