Nobody will tell you what happened to the Jira reports that were retiring on 31 July
Gabriela Perdum
Author
5 min readAugust 31, 2026
Key takeaways
Two batches, opposite answers: Version Report, Epic Burndown and Release Burndown were REVERSED. Time Tracking, User Workload and Version Workload were not.
Atlassian's last word on any of it is 13 July. BOTH dates in circulation — 31 July and 30 August — have now passed with no announcement either way.
The 'it was rolled back' answer is a Community Champion's, given on a thread with no Atlassian post on it.
The '30 August' date comes from two Atlassian Marketplace partners writing on community.atlassian.com. No Atlassian source states it.
The API will not settle it for you: no endpoint lists the old project reports, and the one that does list reports returns the new agility set with no retirement flag.
Somebody asked, in French, on 31 July, what replaces the time tracking report. His words were that access to it disappears "à partir de demain" — starting tomorrow. I answered that thread at the time, which is why I went back to it.
A month later, the honest answer to his question is that nobody will tell you. Two deadlines have now gone by without a word.
That is worth writing down, because three different answers are circulating and not one of them comes from Atlassian.
There were two batches, and they got merged
Six reports were announced. People discuss them as one group. They are not one group.
On 13 July, Ben Payne — posting with an Atlassian Team badge, in what became the accepted answer on the thread where this was being argued out — wrote that because of feedback they would not retire Version report, Epic burndown, Release burndown. In the same breath:
"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"
Three saved. Three kept on the list, with minimal feedback given as the reason — which is an invitation, not a verdict.
The three that were saved are the burndown-and-version family. The three still scheduled are the ones about people and time. If your time report is the one that sprouted a lozenge, you are in the second batch, and the good news you have been reading was about the first.
Worth saying, since it comes up in the same breath: if what you need is the numbers rather than the report, the worklog data is still fully reachable through the API — I wrote up how to get every worklog off an issue recently, including the ones the API quietly withholds.
What happened on 31 July
Nothing was announced. That is the whole event.
People kept asking on the thread. Irina Zdanovych on 21 July, asking about alternatives for Version Workload. Nuno Araújo on 23 July, counting 1,381 issues with logged worklogs across 17+ active projects in a single project category over twelve months, asking for reconsideration. James Clark, an Atlassian Solutions Partner, on 29 July, adding a customer data point "as it sounds like feedback is what decides this one". Two more on 30 and 31 July, and one on 3 August.
Several of them ask the same question: is there a confirmed date. Ben Payne's 13 July post is still the last thing anyone from Atlassian has said on that thread.
Meanwhile people watched the in-product lozenge appear and then vanish again — three separate members describe exactly that, across July.
The three answers going around
Answer one: it was rolled back. The most repeated one. It comes from a Community Champion — a volunteer badge, not an Atlassian one — who wrote, on a thread asking specifically about Version Workload: "The deprecation of the three reports has been rolled back and lozenge has been removed after feedback from customers." That thread contains no Atlassian post at all. The reports Atlassian had rolled back, a week earlier, were the other three.
Answer two: it moved to 30 August. This one is worth tracing, because the trail is short and it does not lead where the search engines say.
Two Atlassian Marketplace partners carry it, both writing on community.atlassian.com — which matters, because that is where a reader meets it and it looks semi-official there. One states it flatly: "The reports were originally scheduled to be retired on July 31, 2026, but Atlassian postponed the retirement until August 30, 2026." The other, three days later, is honest about what it is: "It looks like Atlassian pushed the retirement back in response to user feedback."
It looks like. No source, in either case. I could find no Atlassian statement of a 30 August date anywhere — not in the changelog, not in the Cloud changes blog, not in the docs, not in any Atlassian post. And nobody in any of these threads reports seeing a 30 August lozenge; every sighting anyone describes says 31 July.
That second date has now passed too, and nothing marked it. Checked on 31 August: no new Atlassian post on either thread, no changelog entry, and the documentation page byte-identical to a week ago — still last edited in May. None of that proves the reports survived, for the reason in the next section. It does mean both dates anyone has named, the one Atlassian gave and the one it did not, went by without a word.
Answer three: it is still scheduled and nobody has said otherwise. This is what the evidence supports. It is also the least satisfying, which is presumably why it travels worst.
The documentation will not settle it either
Atlassian's report list still carries all six, with their normal descriptions and no retirement notice anywhere on the page. I checked the raw HTML rather than trusting a summary.
Then I checked when that page was last edited: 29 May 2026 — a month before the lozenges started appearing. So the page's silence is not evidence that the reports survived. It is evidence that nobody updated the documentation. Those are very different findings, and I nearly published the first one.
The API will not settle it either
This surprised me enough to check three ways.
There is no endpoint that enumerates a project's old reports. /rest/api/3/project/{key}/reports returns a flat 404: "No endpoint GET /rest/api/3/project/LZPT/reports."
An endpoint that lists reports does exist — GET /rest/agile/1.0/board/{boardId}/reports, documented as getReportsForBoard. I called it on a live site: HTTP 200, six reports back. But they are the agility reports — burnup, sprint burndown, velocity, cumulative flow, cycle time, deployment frequency — none of the six in question. It works only on team-managed boards; a company-managed board returns a 400 saying so. And no field on any report indicates a retirement.
The old ConfigureReport.jspa URL answers, but under an API token it renders the error page for every report key I passed it, real or invented. So it cannot tell you anything either.
Which means the check every admin actually wants — do I still have this report, and does it have a lozenge on it — has no API behind it at all. You open the Reports tab and you look. On each site, because a lozenge rolling out is not the same as a feature being removed. Time tracking has more of these edges than it should — blocking time logging on specific work types is another one only reachable sideways.
What I would do
If you are on the second batch, the position is: still scheduled, no confirmed date, no announcement either way. Not saved, and not gone.
Go and look at your own site rather than trusting any summary, this one included. If those reports matter to you, say so on the thread — minimal feedback is the stated reason they are still on the list, and feedback is the one input that has already been shown to move this. It moved three reports in July.
And if you are shopping for a replacement because you read that they were rolled back, or that you had until the end of August: check who said it, then check whether the source they name actually says it. On this one, the confident answers and the sourced answer are not the same answer.
