Capacity planning in Jira
Before you commit to work, you need to answer one question: does the plan actually add up, or are you quietly overloading the same people again?
What is capacity planning?
Capacity planning is the process of forecasting the resources a team needs and matching that demand against the time, skills, and availability you actually have. Done well, it tells you whether a team can take on new work without overloading anyone or missing a deadline.
The concept is not new, and it is not unique to software. For the fundamentals, including the difference between capacity planning and resource planning and the common pitfalls, see Atlassian's guide to capacity planning. This guide picks up where that leaves off: how you plan capacity inside Jira, where the work already lives.
Most teams still plan capacity in a spreadsheet that sits apart from their work. It goes stale the moment someone changes projects or takes leave, and by the time the plan is wrong, the overload has already happened. Planning in Jira keeps the plan connected to the work it describes.
Team capacity and individual capacity in Jira
Jira supports capacity planning at two altitudes, and knowing which one you need is the first decision to make. Team capacity looks at a whole team's throughput across a sprint or program. Individual capacity looks at one person's week and what they are committed to.
Team capacity with Plans
Jira Plans handles team-level capacity for agile delivery. You plan in story points or member-weeks and balance a team's committed work against its historical throughput across sprints and programs. This is the right altitude for sprint planning, release planning, and scaling delivery across multiple teams.
Individual capacity with the Capacity view
The Capacity view handles individual-level planning. A people manager or team lead allocates specific people to work items, epic and above, or to non-project time like leave, on-call, and maintenance. Allocations are universal: an allocation you create in one board follows that person everywhere, so you cannot accidentally double-book them across two teams.
The Capacity view brings individual planning into Jira, so managers can see who is working on what, where their time is going, and whether the plan adds up, without leaving Jira.
What you can do in the Capacity view
The Capacity view is a table where each row is a team member or a work item, and each column is a week. You plan from whichever side fits how you think.
Plan from the people side or the work side. Start with a person and see what they are allocated to, or start with a work item and see who is on it.
Allocate capacity by percentage, days, or hours. Set how much of a week goes to a given work item or commitment, one cell at a time.
Account for the work that never makes the plan. Mark leave, on-call rotations, training, and maintenance so the picture is honest. Two weeks of leave adjusts that person's available capacity automatically.
Spot overallocation before it becomes a problem. A capacity bar updates for each person as you plan. When a week exceeds 100 percent, the bar turns red so you can rebalance.
Edit like a spreadsheet, connected to Jira. Copy, paste, drag, and bulk-update cells, but on data that stays tied to real work items and people.
Filter to what you need. Narrow the view by person, work item, status, or work type.
See allocations across spaces. Plans span the site level, so a person's commitments are visible wherever they show up.
How do I choose between team and individual capacity planning?
Choose based on the question you are trying to answer. If you are asking whether a team can commit to a sprint or a release, plan at the team level with Plans. If you are asking whether a specific person has room next week, plan at the individual level with the Capacity view.
Many teams need both. A program lead balances team throughput in Plans, while a people manager on the same program uses the Capacity view to make sure no single engineer is quietly carrying three epics. The two levels answer different questions, and the most common way capacity planning fails is by using the wrong one.
Frequently asked questions
What is capacity planning in Jira?
Capacity planning in Jira is the practice of matching planned work to the people and time available, inside the tool where the work lives. Jira supports it at the team level with Plans and the individual level with the Capacity view.
What is the difference between team and individual capacity planning?
Team capacity planning measures a whole team's throughput across sprints, usually in story points. Individual capacity planning tracks one person's weekly commitments across all their work, so you can see who has room and who is overloaded.
What is the Capacity view in Jira?
The Capacity view is a table in Jira where managers allocate people to work items or to non-project time like leave. Each row is a person or work item, each column is a week, and a capacity bar flags anyone over 100 percent.
Does capacity planning in Jira replace my spreadsheet?
Yes. The Capacity view replaces spreadsheet-based planning, and you can import a spreadsheet to start. Jira maps your data to real work items and team members, so any change updates the plan automatically. No more fixing row 47 by hand.
Who can see and edit a capacity plan?
People managers and team leads build and adjust capacity plans with space admin permissions. Allocations are visible across the site, so a person’s commitments appear wherever they show up – but only users with the right space permissions can edit allocations.