Can we create a Resource Utilization report in Jira Software Cloud?
Does anyone know if this is possible or can point me in the right direction?
Hi Alexander,
In Jira, you could use the standard reports like:
However, Atlassian is retiring these reports on July 31, 2026, so they won’t be available going forward.
As a future-proof replacement, I highly recommend Planyway.
As an alternative, Planyway provides several reports to analyze team utilization and workload:
⬇️ Our workload report:
⬇️ Our Planned vs. tracked report:
⬇️ Our Time Tracking report:
Beyond workload reports, Planyway provides an interactive timeline for drag-and-drop scheduling, cross-project planning views, capacity visibility, time tracking, and team calendar sync — helping teams plan resources, track progress, and manage workloads in one place.
Hope this helps.
Feel free to reach out with any questions or to schedule a Planyway demo.
Best,
Mary.
Hey Alex,
Short answer: there's no built-in report called "Resource Utilization" in Jira Software Cloud, but depending on what you mean by utilization you can get most of the way there with what's already included.
If you want to see how open work is spread across people right now, create a dashboard (Dashboards > Create dashboard) and add the Workload Pie Chart gadget or the Issue Statistics gadget grouped by Assignee. Point them at a saved filter like `project = X AND statusCategory != Done` and you get a live view of each person's open workload.
If you're on a Premium plan, Plans includes capacity management: you can set a team's capacity per iteration (hours or story points) and see allocation vs. capacity on the timeline. That's the closest thing to a true utilization view that Atlassian ships out of the box.
If by utilization you mean actual time logged vs. available hours, you'll need worklog data: make sure time tracking is enabled and the team logs work. The built-in Time Tracking report covers a single project/version, but there's no native cross-project rollup of logged time per person — that's usually the point where teams either export to a spreadsheet or use a Marketplace app.
Full disclosure: my team builds one of those apps (Pallas Charts). If you end up wanting something like hours logged per person per week as a dashboard chart without spreadsheet exports, that's the kind of thing it handles.
But I'd try the native gadgets and Plans first — for a lot of teams they're enough.
Cheers,
Anderson
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexander, the User Workload Report is the closest built-in one, and it stops short of utilization. Atlassian's own wording is the ceiling, the number of unresolved work items assigned to the specified user and the remaining workload, per space. Allocated work. Nothing to hold it against. Plans won't close that either, capacity there is a team number for the sprint.
Mary's 31 July is less settled than the lozenge makes it look. Three in the same batch, Version Report, Epic Burndown and Release Burndown, were pulled back after people pushed on the thread below, where Ben Payne of Atlassian wrote that for the remaining three, Time Tracking, User Workload and Version Workload, they "will still schedule them for deprecation unless we hear more from users and the community". No date confirmed since.
So per-person utilization is marketplace territory, which is what the two replies above are offering. That thread is where the native side gets decided.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alexander !
Out of the box, Jira Software Cloud doesn't have a resource utilization report — native reports (Burndown, Velocity, Sprint Report) focus on issue progress, not on people's capacity vs. allocated hours. For utilization you'll need an app.
We'd recommend our tool ActivityTimeline — it's built exactly for this. Its Resource Utilization Forecast report shows each team member's total available capacity (full capacity minus vacations, sick leave, and other time off), how many hours are actually allocated to them, and the resulting utilization rate — broken down day by day, week by week, or month by month, so you can spot over- or under-utilization in advance.
To generate it: Reports → Resource Reports → Resource Utilization Forecast, then set:
After the report is generated you can adjust everything on the fly (period, units, filters, hours vs. percentages, whether to include Jira issues, placeholders, and bookings) and export it to Excel or view it as a web report.
Data comes from remaining estimates, daily estimates or story points of tasks scheduled on the timeline, plus bookings and placeholders — so it covers non-Jira work too.
A few related reports worth checking if you need a different angle:
One config note: if your team logs worked time, keep the "Users log worked time" option on and the forecast will cover the present and future (past data lives in worklogs / Team Timesheets). If you estimate with Story Points or Daily Estimate, select "Users do not log worked time" so the report also shows past periods correctly.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hola Alexander,
Could you clarify what you mean by “resource utilization”? For example, are you trying to compare planned capacity against assigned work, report on time logged by each person, identify overallocated team members, or measure completed work over a specific period?
It’d also help to know which Jira Cloud plan you’re using, whether you have Jira Plans or any time-tracking apps installed, and what data you currently capture on issues. The available options depend heavily on whether you’re measuring estimates, logged time, story points, or scheduled capacity.
Thanks,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.