RFC 120 - Individual capacity planning in Jira Cloud

Summary of Project

We are creating a new experience in Jira to enable capacity planning at the individual level.

The goal of the experience is to enable people managers and team leads to plan capacity of individuals in their team across major work streams and define their allocation against each. These major streams of work can be modelled as Jira epics or higher-level work items.

We are working towards a closed EAP with a limited set of features for a few customers by the end of 2025, followed by an Open EAP in April–May 2026.

We don’t currently have APIs or UI extension points in Connect or Forge; however, we’re committed to building an extensible experience and plan to provide these extension points in the coming months. We’d love your feedback on how we can provide value to both existing and new apps.

  • Publish: Nov 17, 2025
  • Discuss: Dec 1, 2025
  • Resolve: Dec 15, 2025

Problem / Opportunity

Today, customers manage individual capacity and allocations outside Jira—using spreadsheets or external platforms. This fragments data: work planning lives in Jira, while people planning is disconnected, making it hard to get a real-time and accurate view of who is working on what, and when.

Capacity planning is a fundamental part of project management, and we are increasingly hearing from customers the need for an out-of-the-box solution.

To address this need and to maintain Jira’s leadership position in the market of being the best project management tool of choice for ‘all’ teams, we’re building a native individual capacity planning experience that’s accessible to everyone. The experience is designed to address the most common use cases, and we’ll work closely with Marketplace partners to provide extension points, so the experience can be enhanced with deeper functionality and tailored to specialised needs.

Proposed Solution

We are adding a new view called Capacity in Jira Space (previously known as Jira Project), alongside other views like List, Board, etc.
People managers and team leads can, at the start of the planning cycle, assign individuals to high-level work defined in Jira - epics or higher.

Below are some of the experiences we plan to ship between now and May’2026

Now [end of 2025]

  1. Capacity View in Jira Space, allowing individuals to be mapped to Jira epics and higher-level work items, along with their allocation in % to each

  1. Ability to capture leave and non-project work, like Training, BAU (business as usual) work

Later ( preliminary and subject to change)

  1. Time-based allocations: Supporting individual allocations in time (hours, days, weeks), anchored to each individual’s configurable overall capacity (default 40 hours/week, editable).

  2. Work first resourcing view - Start with the work and its estimated effort, then allocate individuals accordingly to forecast delivery timelines and assess what’s achievable within available capacity.

  3. Enhanced usability and AI: Usability improvements and AI-assisted capacity planning

Other key callouts

  • The experience is envisioned to allow capacity planning against big streams of work and hence supports Jira epics and higher-level work items, not below work items.

  • The capacity view will be available in all types of Jira spaces - company-managed, team-managed, as well as business and software spaces.

Asks

We welcome your feedback and suggestions to help refine our solution, and are committed to building an extensible experience. We would specifically appreciate your feedback on:

  • What APIs or UI extension points would help make your current apps better?

  • What APIs or UI extension points would be useful for creating new app opportunities?

20 Likes

Some directions what to include based on experience with this kind of data.
APIs for integration with Human Resources systems.
Like: Contracted hours, bank holidays, vacations, overtime.

APIs to extract the data for Power BI reports.

Reports to compare planning VS actual.
Reports to present available not planed capacity.

3 Likes

Hi Team, is there EAP sign-up link? or how can I enable this feature on my site?

1 Like

Consider enabling capacity to be mapped at all work item hierarchy levels, not just Epics and above. For example, if a user is assigned to 3 Stories, I would want to be able to plan their capacity against those Stories, not just the Epics that they roll up to.

8 Likes

The greatest value of capacity planning is the ability to see how that plan maps to what happened. Is this that the work first resourcing view will be for? Will this be for below the Epic level, allowing for a rolled up view?

This new Individual Capacity Planning direction looks great and will address a long-standing gap in Jira. As you continue shaping the feature, it would be extremely helpful to understand the planned API model so Marketplace partners and Forge developers can begin preparing compatible solutions ahead of launch.

A few API considerations that would greatly benefit app builders:

1. Capacity Data Endpoints

• Ability to retrieve a user’s capacity for a given date range, sprint, or project

• Access to user-level schedules (work hours, exceptions, holidays, absences)

• Team or project-level capacity summaries

• Iteration-level capacity (sprints or custom cycles)

2. Workload & Issue Context

To support capacity-based recommendations and reporting, extensions to issue APIs or new endpoints exposing:

• Issues/Epics with estimates but no assignee

• Roll-up of estimates across the issue hierarchy

• Ability to correlate workload vs. available capacity windows

3. Assignment Intelligence

Support for surfacing available resources based on capacity, schedule, or skills/attributes (including data from custom fields or directory metadata).

4. Multiple-Resource Assignment

Many teams split work across multiple contributors. It would be great to understand whether fractional or multi-person assignment is part of the long-term roadmap for capacity planning.

5. Extending Hierarchy Support Below Epics

Echoing a point raised in another comment: it would be extremely useful for capacity considerations to extend not only to Epics and above, but also down into the full parent/child structure (e.g., Story/Task → Subtasks). This reflects how most teams distribute work and would significantly improve accuracy in capacity forecasting.

6. Additional Consideration: Goals API Support

As Goals become more integrated into Jira’s planning ecosystem, it would be valuable to know whether the capacity APIs will also surface:

• Goal relationships for Epics and Initiatives

• Goal-level metadata (status, timeframe, owner, progress)

• A consistent hierarchy model that includes Goals

This would allow apps to connect capacity constraints to strategic objectives and identify Goals at risk due to insufficient available resources.

These API surfaces would enable developers to build deeper capacity-planning solutions, mobile experiences, and integrations with products like Tempo. Looking forward to more detail on the data model and any update capabilities in future iterations.

2 Likes

Is this an RFC or are you actually shipping part of this already? “Now [end of 2025] → Capacity View in Jira Space…” - Looks very interesting!

Great news! I want to ask how to sign up for EAP?

2 Likes

Would love to get on the EAP for this one!

1 Like

This is going to be a game changer for teams , how can we subscribe to the EAP to try it out and provide feedback? @TejasvitaMadan

1 Like

A pull of external dat would be very nice. Often holiday requests are down in a separated system. And people are assigned to an on duty rotation in opsgenie. Etc etc

So standard sync capabilities would be very welcome

1 Like

Will this be available to all tiers or Premium/Enterprise only? Thank you!

How are you defining capacity planning? Ensure you differentiate between capacity planning and resource allocations which are different when thinking about the business requirements.

In my view:

Capacity planning: Capacity planning is high-level and strategic in nature, focused on medium to longer-term time horizon (quarters, years). It ensures the organization has enough overall capacity (people, time, systems, budget, infrastructure) to meet forecasted demand. This typically should be done in annual planning and quarterly refreshes, and answers the question “Do we have enough?”.

On the other hand, resource planning, is more detailed and operational, allocating specific resources to specific work, tasks, projects over a short- to medium-term (weeks, months) time horizon. This should be done more ongoing, often monthly / sprint-based / project-based. The question to answer is “How do we allocate what we have?”

We are looking forward for the feature and would like to subscribe to EAP to try this out.

We would like API that would give request data in batches and per individual user/ticket for reporting.

Capacity data endpoints

  • bulk fetch ability to request capacity data for several spaces, users, period

  • bulk fetch additional filters by last updated data

  • issue bulk search response per ticket could include capability block

  • ticket json could include capacity block

  • capacity data response could split data per user per day per one planning item (epic, ticket)

1 Like

Thank you for the question @JihanCardenas
This is something we are actively evaluating; however haven’t finalised the decision yet.
I’ll share an update as soon as we do.

Thank you @BradWood

Great feedback. We will consider this for our future milestones

Hey @LukasGotter - We’re planning a limited feature rollout to a closed EAP group in late December to gather some early feedback.

Thank you, let us know how we can join the EAP, these features sound pretty exciting!

This is exciting. For me as a battle scarred Portfolio (insert label) may I ask … will we be able to do EVM /SPI / CPI at some point……

Quick question: Since now, are there plans to extend this capacity view for Plans to enable cross capacity project planning?

1 Like