Resource Utilization Tracking for Jira Teams in ActivityTimeline
See how much of each person's and each team's available time goes to work: planned for the weeks ahead, logged for the weeks behind, and where the two parted. Straight from your Jira estimates and worklogs.
30-day free trial on the Atlassian Marketplace.
Planned utilization per person and team, weeks before the work starts
Actual utilization from the hours logged in Jira
Planned vs actual, down to the person, project and issue
Three ActivityTimeline reports. Resource Utilization Forecast for a Platform team of four over the next four weeks: the team is planned at 71 to 97% a week, but Ana, Tom and Priya each go over 100% in at least one week; Tom reaches 125% in the week of 23 November. Team Capacity Chart for an Infrastructure team, by month from December 2026 to May 2027: the cloud migration and a security audit peak together, so February, March and April need 670 hours more than the team has, with March at 131% (1,300 hours planned on 990 available), while December and January still have 340 hours free. Project Resources Forecast for the Platform team: Website and Mobile app have three people each, while all 78 hours of Platform ops sit with Tom.
Three featured reports, three questions: who is overbooked next week, which team runs out of room next quarter, and which project hangs on one person. All from the work already planned in Jira, against the hours people really have.
What Resource Utilization Means in ActivityTimeline
The share of each person's available time that goes to work, before the weeks start and after they end. Pick a person and week to see how it adds up.
Tom Becker, week of 23 November: a 40-hour working week minus 8 hours of Thanksgiving leaves 32 hours of available capacity. He has 40 hours of planned work (20 hours Platform ops, 16 hours Website, a 4-hour support rotation), so his utilization is 40 ÷ 32 = 125%.
Ahead
Who is overbooked next month?
Resource Utilization Forecast: planned work against available capacity, per person and team, week by week.
Behind
Where did the hours go?
Team Utilization Pie Chart: a team's logged hours split by project, epic or Jira field.
Against the plan
Did the estimates hold?
Planned vs Actual Chart and Report: capacity, scheduled and logged time, down to the issue.
Popular capabilities
What You Can Do with Resource Utilization in ActivityTimeline
The featured reports behind resource utilization, ready on the first day. Each reads the plan your teams keep in ActivityTimeline and the hours they log in Jira, so nobody fills in a spreadsheet first.
See every report in ActivityTimeline ReportsResource Utilization Forecast
See each person's and team's planned utilization for the weeks ahead, by day, week or month, in hours or percent.
Team Capacity Chart
Compare a team's available, utilized and remaining capacity week by week or month by month.
Project Resources Forecast
See who is committed to each project and for how many hours, week by week.
Planned vs Actual Report
Compare estimates with time spent per issue, epic or project, and see which work ran over your acceptable deviation.
Planned vs Actual Chart
Put team capacity, scheduled time and logged time side by side, week by week or month by month.
Team Utilization Pie Chart
Split a team's hours by project, epic or a Jira field, for a past period or the weeks ahead.
Team Utilization Forecast
See how each team's capacity splits across projects, initiatives or epics in the weeks ahead.
Utilization on Jira dashboards
Add reports to Jira dashboards as gadgets, embed them in Confluence, or export them to Excel.
How to Track Resource Utilization in ActivityTimeline
From the weeks ahead to what actually happened, and back into the next plan. Every step uses data your teams already keep in Jira.
Forecast Utilization Before the Work Starts
The Resource Utilization Forecast puts every person and team against the weeks or months ahead and colors each cell by how full it is. Spot the red cells early, then fix them on the Planner while there is still time.
Planned hours from assigned Jira work items, bookings and placeholders
Capacity net of time off, holidays and part-time schedules
Group by person to see the projects behind a red cell, or by project to see who carries it
Resource Utilization Forecast for the Platform team, 16 November to 13 December 2026, by week. Tom Becker is at 125% in the week of 23 November: 40 hours planned on 32 available because of Thanksgiving, made of 20 hours of platform ops work, 16 hours of website work and a 4-hour support rotation booking. Grouped by project, Platform ops has 78 hours over the four weeks, all of them Tom's.
Measure Actual Utilization from Jira Worklogs, Then Compare It with the Plan
Once the weeks have passed, see how they went. Compare logged time with capacity for actual utilization, or with the plan to see which work slipped. Save both views with your filters and open them at every review.
Team capacity, scheduled time and logged time, week by week or month by month
Issues, epics or projects that ran over their estimate
An acceptable deviation you set, so only real gaps stand out
Team Planned vs Actual Chart for the Platform team, eight weeks from 14 September to 6 November 2026: 1,184 hours of capacity, 1,152 hours scheduled and 1,064 hours logged, which is 89.9% actual utilization and 92.4% of the plan. In the week of 21 September the plan asked for 176 hours from a team with 152, and the team logged 164, or 108% of capacity. In the week of 5 October the team logged 96 of 152 hours, 63% of capacity and 36 hours short of the plan.
See Where the Time Went, and Plan the Next Weeks on It
The Team Utilization Pie Chart splits a team's hours by project, epic or a Jira field: logged time for a past period, planned work for the weeks ahead. Put the two side by side to see whether the time went where you meant it to.
Logged hours for any past period, planned hours for the weeks ahead
Split by project, epic or any Jira field
Recurring unplanned work, like support, goes into the next forecast as a booking
Team Utilization Pie Chart for the Platform team, grouped by project. Last four weeks, from 540 logged hours: Mobile app 200 hours, Website 184, Platform ops 88 and the support rotation 68, which is 12.59% of the team's time. Next four weeks, from 482 planned hours: Website 180, Mobile app 176, Platform ops 78, support rotation 32 and a 16-hour placeholder for the payments revamp.
Talk to a product specialist
Have Questions About Your Utilization Numbers?
Bring one department to a 25-minute demo. A product specialist builds its utilization view with you from your own Jira data, and answers your rollout, security and licensing questions.
What we cover in 25 minutes
Next month, planned
0–10 min. Utilization per person and team from your Jira estimates.
Last month, logged and against plan
10–18 min. Actual utilization and where it parted from the plan, from your worklogs.
Your rollout
18–25 min. Security review, licensing at your user count, and where to start.
Guides and Comparisons
How-tos for planning, utilization and time tracking in Jira itself live in the guides. Comparisons with other tools live in their own section.
Guide
Resource utilization in Jira
The formula, benchmarks, planned vs logged, and where native Jira stops.
Read the guideGuide
Capacity planning in Jira
How to plan team capacity in Jira, and where utilization fits in.
Read the guideGuide
Time tracking in Jira
Logging time in Jira, and the worklogs actual utilization is built on.
Read the guideCompare
ActivityTimeline as a Tempo alternative
Side by side with Tempo for Jira, and how teams switch.
See the comparisonResource Utilization in ActivityTimeline: Questions
Answers about planned and actual utilization, the reports behind them and who can see them.
More answers in the Help CenterSee Your Team's Utilization, Ahead and Behind
Install ActivityTimeline from the Atlassian Marketplace, connect one team and see next month's planned utilization from the Jira estimates you already have. Add logged time to see actual utilization and how it compares with the plan.
A Jira dashboard with two ActivityTimeline gadgets for the Platform team: the Resource Utilization Forecast for the next four weeks and the Team Planned vs Actual Chart for the last four.
