Dashboard PlanCapacity planningwith Planner and Reports

Capacity Planning for Jira Teams in ActivityTimeline

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.

Trusted by 10,000+ teams around the world

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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%.

Sprint, quarter, half-year

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.

Sprint · 1–2 weeks

How much can we really finish this sprint?

Remaining estimates or story points
Each person against hours left
Sprint guide→

Quarter view: team workload by month against a 100% capacity line, with February at 114%.

Quarter · 3 months

Which team can take which initiative, and when?

Teams first, people later
Placeholders for tentative work
Quarterly planning guide→

Half-year view: skill availability by month for Java, React and QA, with a future Java hire planned from April.

Half-year and beyond

Do we have the people and skills for next year?

Skill and role availability
Future hires as resources
Long-term planning guide→

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.

Capacity Planning in ActivityTimeline: Questions

More answers in the Help Center.

What is capacity planning in ActivityTimeline?
It is comparing the work planned for each person and each team with the hours they really have. ActivityTimeline takes planned work from all your Jira projects, plus bookings, placeholders and calendar meetings, and available hours from each person's work schedule, public holidays and time off. A workload indicator under every name shows who is over and who has room, and Reports forecast the same plan by week or month.
Do we need to track time to plan capacity?
No. Capacity planning works on estimates and the hours people have, and many teams use ActivityTimeline only for planning. If your team also logs time, you can compare the plan with what really happened in the Planned vs Actual report.
Can we plan work that isn't in Jira yet?
Yes. A booking reserves hours per day for a project or a duty, for one person or a whole team. A placeholder holds tentative work with a total estimate. Both count toward capacity from the day you add them, and approving a placeholder turns it into a Jira issue.
Can several people work on one Jira issue?
Yes. Split the issue into parts. Each part has its own person, dates and hours, counts toward that person's workload, and stays tied to the original issue. Splitting works on issues estimated in hours.
We already plan in Jira Plans. Do we need both?
Many teams keep Jira Plans for roadmaps, dependencies and releases, and use ActivityTimeline to check whether the people have the hours to deliver them. Both work on the same Jira work items, so nothing is entered twice.
How do we try it?
Start a 30-day free trial from the Atlassian Marketplace on your own Jira projects. Or schedule a demo, and a product specialist shows capacity planning on a team like yours.

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.