See each person's real capacity next to all their planned Jira work, and fix overload before the sprint starts.
- Real hours per person
- Every Jira project on one plan
- Overload spotted weeks ahead
Planner, Platform team, week of 23 November: three people's planned work against their hours. On paper everyone has 40 hours and the team is 70% full. With Ana's two days of vacation and Tom's four-day week, both are over. Moving one task to Emma and splitting another brings everyone under 95%.
Same team, same week, three views. A headcount plan gives everyone 40 hours. ActivityTimeline counts the hours people really have, so overload shows up before the week starts.
What Capacity Planning Means in ActivityTimeline
Capacity is how much each person can really work. Put their planned work against it to see who has room and who is overloaded.
Sample week for a team of five. Real capacity: 200 hours on paper, minus a public holiday (16 h), vacation (16 h) and a four-day week (8 h), leaves 160 hours. All planned work: Jira work items 120 h, meetings 14 h, bookings 10 h and placeholders 24 h make 168 hours. What is left: 8 hours over, 105% of real capacity.
How to Plan Capacity in ActivityTimeline
Use this four-step framework to go from the hours people really have to a plan, and a forecast, you can stand behind.
Start from each person's real capacity
Work schedules cover part-time, four-day weeks and regional working days. Public holidays come from a holiday calendar per country, and vacations, sick leave and days off take hours out of the days they fall on. Set it once per Jira group, and everyone in the group gets it.
Tom's capacity for the week of 23 November: 40 hours on a standard week, 32 on a four-day week, 24 after Thanksgiving, 20 after a half day off.
Put all planned work against it
Everything that takes someone's time lands on the same timeline: Jira work items from every project, with story points converted to hours, meetings from Google Calendar or Outlook, bookings for recurring duties, and placeholders for work that isn't in Jira yet. Approve a placeholder, and it becomes a Jira issue.
Emma's next four weeks: Jira work from two projects, a support-rotation booking, meetings from her calendar, and a placeholder for work that is not in Jira yet, with weekly workload against 40 hours.
See who is over, from teams down to people, and rebalance
Start with teams: their workload and free hours week by week or month by month, with work held on a team before anyone is named. Open a team that turns red to see who is behind the number. Then move work to another person or week, split one issue between people, or shift a delayed project's items all at once.
Teams view, December to March: workload against capacity for the Platform, Mobile, Data and QA teams by month, with the people behind each number.
Forecast the quarter and report it
Reports turn the same plan into answers for leadership: available, planned and remaining hours per team, each person's utilization for the weeks ahead, and who with a given skill or role is free. Count tentative work or leave it out, and see where the squeeze starts. Share it on Jira dashboards, in Confluence or in Excel.
Team Capacity Chart, Platform team, January to June: confirmed work fills 91% of January and falls to 26% by June; with tentative work added, February reaches 114%.
What You Can Do with Capacity Planning in ActivityTimeline
Every capability below is part of Planner or Reports. Open a card to see how it works.
Workload indicator
See who is over or under capacity, under every name, by day or week.
Work schedules
Plan part-time people, four-day weeks and regional working days on the hours they really work.
Holidays and time off
Take public holidays by country, vacations, sick leave and days off out of capacity.
Calendar sync
Bring meetings from Google Calendar or Outlook onto the timeline as busy time.
Bookings
Reserve hours per day for a project or a duty, for one person or a whole team.
Placeholders
Plan work that isn't in Jira yet, then turn it into a Jira issue with one approval.
Split a task between people
Share one Jira issue between several people, each with their own dates and hours.
Story points to hours
Count point-estimated work toward capacity with a ratio per project.
Team-level planning
Plan against a team's capacity first, and hand the work to people later.
Resource Utilization Forecast
Forecast each person's workload against their capacity, week by week.
Team Capacity Chart
Compare available, planned and remaining hours per team, by week or month.
Skill and position availability
Find who with a given skill or role has hours free, and when.
Capacity Planning at Every Horizon
One plan, three questions, depending on how far ahead you look.
Sprint planning view: three people across one week, one of them at 10 hours a day and flagged as overloaded.
Quarter view: team workload by month against a 100% capacity line, with February at 114%.
Half-year view: skill availability by month for Java, React and QA, with a future Java hire planned from April.
No timesheets needed to plan. Capacity planning runs on estimates and the hours people have. Add time tracking when you want to compare the plan with what really happened.
Have Questions About Your Setup?
Bring one department to a 25-minute demo. A product specialist shows its real capacity for next quarter in ActivityTimeline, and answers your rollout, security and licensing questions.
Guides and Comparisons
How-tos for planning capacity in Jira itself live in the blog. Comparisons with other tools live in their own section.
Illustration of a guide page with a capacity chart.
Jira capacity planning: the complete guide
Native Jira, Jira Plans, where they stop, and a capacity calculator.
Illustration of a sprint board.
Sprint capacity planning in Jira
Why green workloads still miss deadlines, and how to plan on real hours.
Illustration of two tools side by side.
How ActivityTimeline compares
Side by side with other capacity planning tools for Jira, and how to switch.
Illustration of a three-step setup.
Scenario: forecast next quarter's capacity
The step-by-step setup in ActivityTimeline, for admins and planners.
See Your Teams' Real Capacity for Next Quarter
Install ActivityTimeline from the Atlassian Marketplace, connect a team, and see who is over and who has room on your own Jira data.
- 30-day free trial on the Atlassian Marketplace
- Works on your existing Jira projects, issues and estimates
- Start with one team, roll out to the whole company
Built with Planner and Reports. Add Workspace and Timesheets when you want planned vs actual.
Team summary for the Platform team after rebalancing: from the week of 30 November the team has 65 to 82 free hours a week for new work.