Jira’s Time tracking report and its alternatives

Jira’s Time tracking report compares estimates with the time spent on a version’s issues. In July 2026 Jira’s Reports page marked it as retiring, and people asked “what I can use to get the same insights?” (Community, July 2026). This page says what the report does and where it stands, how to compare estimates with time spent using Jira’s own search, then what Logline does.

What the report does, and where it stands

• One version at a time, in company-managed spaces. It compares the estimates of a version’s issues with the time spent on them (Atlassian). Team-managed spaces do not have it; the request, JSWCLOUD-18009, has been open since 2019. It does not split the time by person or by month.
• On Atlassian’s list to retire. Time Tracking, User Workload and Version Workload were marked as retiring in July 2026. On 13 July 2026 Atlassian answered on Community that three other reports would stay, after people said they needed them, and that these three “will still schedule them for deprecation unless we hear more from users and the community” (Community, July 2026). The thread names no date. If your teams rely on the report, that thread is the place to say so.

Estimates against time spent with Jira’s search

• A filter for the version in the list view, such as fixVersion = "1.4", with Original estimate, Time spent and Remaining estimate as columns. Σ Time Spent adds each issue’s sub-tasks to its own time. Export it to CSV for the version’s totals.
• The issues over their estimate: workRatio > 100. Jira works the ratio out as time spent over the original estimate, times 100 (JQL fields).
• On a dashboard, the Filter results gadget shows either list.

Where it stops: every figure is all-time and per issue, so none of them says how much went in last month, or who logged it. Time logged per epic in Jira covers how far Jira adds a child’s time into its parent.

With Logline

Logline is our app. It works from the worklogs over a period you pick, and puts the estimate beside them:

• Overspend, a switch above the timesheet, adds the Work ratio column for issue rows and marks every issue over its original estimate with its share in red, such as 117%.
• Extra columns, under Edit report › Columns and counting, for issue rows: Original estimate, Remaining, Time spent (all time) as Jira shows it, and Work ratio (all time), beside the period’s hours.
• The Logline panel on any issue sums it up, such as “14h logged of 12h estimate · 2h over”, then the remaining estimate with a forecast, such as “12h remaining · forecast 26h, 14h over”. On an issue with children the estimate includes theirs, and says “(with children)”. Under it, the time by person and the hours logged in each of the last 8 weeks.

With Rows on Epic, then Issue, or on Person, then Issue, the same columns show where the time over the estimate went, and who logged it.

What it does not do: Logline does not group by version, and a report lists only issues with time logged in its period. For a version with every issue, logged or not, Jira’s filter above stays the way.

The marks are described in Gaps and overspend and the extra columns in Rows and columns. More on the Logline home page.