Jira capacity management: a complete breakdown of Jira’s new board-level capacity feature
Capacity planning in Jira has long been a source of frustration for team leads, project managers, and operations administrators. The frustration is not local to Jira. In Wellingtone’s tenth annual State of Project Management survey, poor resource management ranks as the third largest project management challenge organizations report.
Atlassian’s new Jira capacity management feature introduces a dedicated Capacity tab directly inside project and board views. This native addition aims to bridge the gap between execution and resourcing. However, like many newly rolled-out native capabilities, it comes with specific trade-offs, strengths, and sharp boundary conditions.
This guide provides a comprehensive breakdown of what Jira’s native board-level capacity management feature offers, what it cannot do in its current state, how it compares to popular Marketplace solutions like the Capacity Tracker app, and where it fits alongside Jira Plans. Everything below describes the feature as it stood in September 2026.
Key takeaways
- The Capacity tab is a resource allocation model, not a capacity measurement tool. It compares assigned load against a baseline assumption rather than a custom baseline you set per person.
- It tracks an individual’s work across all of Jira on a weekly unit, not one sprint and not one board.
- It runs independently of the Jira Assignee field. Allocating work in the capacity matrix does not update the assignee, and setting an assignee does not populate a capacity allocation.
- No story points, and a fixed 40-hour FTE baseline that cannot currently be customized for part-time employees or contractors.
- Jira Premium and Enterprise only. It is supported on team-managed, company-managed and business projects alike.
What is Jira’s native capacity management feature?
The new native capacity feature introduces a dedicated Capacity tab on project boards. Its primary objective is resource allocation: giving managers a visual mechanism to assign and review individual workloads against expected capacity without leaving the board view.
Key capabilities: what it can do
Cross-Jira visibility for individuals
Unlike traditional board views that confine workload calculations to a single sprint or project, the new capacity view tracks an individual’s work across all of Jira. If a developer or designer is assigned tasks across multiple projects, boards, and sprints, their total aggregated load is pulled into a single consolidated view.
Aggregated personal load and over-capacity warnings
The feature calculates total workload against a full-time workload baseline. When an individual’s assigned effort exceeds standard capacity (passing the 40-hour threshold), the UI visually flags the over-allocation, highlighting potential delivery risks early.
Deviation metrics (time spent vs. original estimate)
To evaluate estimation accuracy, the capacity view includes a deviation metric. It compares actual time spent against the original estimate on work items, giving team leads a real-time variance check on ongoing effort.
Time off and absence tracking
Availability management is built directly into the interface. Managers can record scheduled time off for team members, automatically adjusting their available capacity for specific weeks.
Importing effort and resource allocations
To avoid manual data entry when setting up allocations, the feature supports importing resource and effort data directly into the capacity workspace.
Weekly planning cadence
Allocations and capacity calculations are structured on a weekly unit basis, making it tailored for weekly iteration planning and continuous resource scheduling.
Granular filtering
Although it tracks global individual workloads, the view provides flexible filtering. Users can filter views by person, work item, project, status, and other key issue attributes.
Kanban and Scrum support
The Capacity tab is available across both Scrum and Kanban project boards, enabling continuous flow teams to benefit from resource visibility alongside sprint-based teams.
Native Jira Teams integration
When grouping people into teams within the capacity view, the feature directly uses native Jira Teams rather than requiring local, isolated team definitions.
Team-managed, company-managed and business projects
Unusually for a new Jira planning capability, project style is not a gate here. Atlassian’s launch FAQ answers the question "Which space types support this?" with "Team-managed, company-managed, and business spaces in Jira Cloud." The gate is the plan tier, not the project type.
Current limitations: what native Jira capacity cannot do
The technical details and limitations described below reflect the feature state at the time of writing and may change as Atlassian continues developing the tool.
Despite its strengths in providing global individual visibility, the native capacity feature has several strict technical constraints that Jira administrators must account for:
No linkage to the Assignee field
At the time of writing, resource allocation in the Capacity view operates independently of the standard Jira Assignee field. Allocating work within the capacity matrix does not automatically update issue assignees on the board, nor does setting an assignee automatically populate their capacity allocation. Atlassian documents neither behavior, so this one comes from working in the feature rather than from a support page.
No story point support
The feature relies strictly on time and percentage-based allocations. If your teams estimate work using Story Points, native board capacity management cannot evaluate or burn down those estimates against individual bandwidth.
Fixed 40-hour FTE baseline
The tool automatically assumes a standard Full-Time Equivalent (FTE) capacity of 40 hours per week per person. At present, this default capacity baseline cannot be customized for part-time employees, contractors, or team members with alternate working hours.
Currently, plans use a fixed 40-hour work week and don’t reflect your time tracking or working days settings.
Lack of team-specific separation
Because the feature provides cross-Jira visibility across an individual’s entire workload, there is no native separation or isolation for specific teams inside the global capacity view. This all-Jira visibility can create clutter when managing large multi-team departments.
No granular permission controls
The view currently lacks fine-grained permissions. You cannot easily restrict who can edit or view capacity allocations independently from standard project board access.
Resource allocation vs. true capacity measurement
The tool functions primarily as a resource allocation model. It compares assigned load against expected baseline assumptions, rather than allowing teams to set precise custom capacity baselines and measure real-time sprint execution against them.
Plan tier restrictions
Native board capacity management is available exclusively on Jira Premium and Jira Enterprise plans. Standard and Free tier instances do not have access.
Native Jira capacity management vs. Capacity Tracker (Marketplace app)
For teams evaluating whether native Jira capacity management meets their needs or if they still require an Atlassian Marketplace app, the Capacity Tracker app by Inprowiser Engineering represents a widely used benchmark.
While both tools support Kanban boards and allow grouping individual contributors into teams, their underlying architecture and workflows differ significantly:
| Feature / dimension | Native Jira board capacity | Capacity Tracker (Marketplace app) |
|---|---|---|
| Tier & plan availability | Requires Jira Premium or Enterprise. | Available across all Jira tiers (Free, Standard, Premium, Enterprise, Data Center). |
| Work assignment linkage | Independent of the Jira Assignee field (at time of writing). | Directly driven by the Jira Assignee field. |
| Estimation units | Time, percentage and weekly allocations only. No Story Points. | Full support for both hours and Story Points. |
| Scope & focus | Cross-Jira global individual tracking on a weekly basis. | Sprint-specific capacity management, focused on single-sprint resource balancing. |
| Capacity baselines | Fixed 40h/week FTE baseline, cannot be changed currently. | Fully customizable per-person capacity settings for each sprint or iteration. |
| Team architecture | Uses native, centralized Jira Teams. | Uses internal team entities defined locally within the app. |
| Permission controls | Standard board access, no granular capacity permissions. | Includes dedicated read/write permission controls. |
Key takeaways from the comparison
Use native Jira capacity management if you are on Jira Premium or Enterprise and need cross-project, high-level visibility into where an individual’s time is allocated across the entire Jira instance on a weekly unit basis. The row that decides it is scope. This is the only one of the two that answers a question spanning projects you do not personally run.
Use Capacity Tracker if you need precise, sprint-level capacity planning tied directly to issue Assignee fields and Story Points, or if you operate on Jira Standard and Free tiers or Data Center environments where native board capacity is unavailable. The two tools disagree about what a capacity number is for, which is why the table is not a scorecard. Atlassian’s answer is forward-looking and coarse. Capacity Tracker’s is immediate and precise. A team that plans quarterly and commits fortnightly has a real case for running both.
How board capacity relates to Jira Plans (Advanced Roadmaps)
A common question among Atlassian architects is how board-level capacity management interacts with Jira Plans (formerly Advanced Roadmaps).
Capacity at the Plans level
In Jira Plans, capacity management operates at the macro or sprint level. It evaluates capacity based on the Team field assignment across iterations, allowing portfolio managers to calculate velocity, estimate delivery windows across multiple epics, and balance commitments across multi-project initiatives.
Why Jira Plans remain essential
Even if your team adopts board-level capacity management, Jira Plans remain necessary for several reasons:
Structured team-level rollups. While the board-level Capacity tab offers deep individual filterability (by person, work item, project, or status), breaking down aggregate workload across an entire engineering department or ART (Agile Release Train) is far cleaner inside Jira Plans.
Cross-project alignment and dependencies. Board-level capacity focuses on allocation mechanics. Jira Plans remain the definitive tool for visual dependency mapping, scenario planning, and aligning joint efforts across interconnected releases and projects.
Sprint-level team velocity. Plans measure capacity against sprint velocity and team commitments, whereas board capacity provides a weekly resourcing snapshot for individuals.
Rather than competing, board capacity and Jira Plans serve complementary roles. Board capacity offers team leads micro-visibility into personal weekly bandwidth across projects, while Plans provide portfolio leaders macro-visibility into multi-team delivery timelines.
Summary: choosing the right Jira capacity approach
Mastering Jira capacity management requires matching your operational requirements with the right native or Marketplace capability:
- Native board capacity
- Best for team leads on Premium or Enterprise plans needing quick, weekly cross-project individual resourcing visibility directly on boards.
- Capacity Tracker app
- Best for Scrum Masters and Project Managers requiring tight sprint-level capacity planning tied directly to issue assignees, story points, custom FTE limits, and explicit permission controls across any Jira tier.
- Jira Plans (Advanced Roadmaps)
- Best for release managers and executive stakeholders executing cross-project portfolio roadmapping and team-based velocity planning.
By understanding the exact boundaries of Atlassian’s native board capacity feature, you can build a reliable capacity planning framework that keeps your team balanced, realistic, and focused on predictable delivery.
Frequently asked questions
Does the Capacity tab replace Jira Plans?
Can I use Jira capacity management if my team estimates in story points?
We have part-time staff. Is the tool unusable?
Does it change who work is assigned to in Jira?
If you are trying to work out whether the native tab covers you, whether a Marketplace app fills the gap, or whether the honest answer is a small Forge app that reads your own working patterns, tell us what your week actually looks like.