Hi @Tejasvita Madan , It’s great to see the team tackling individual capacity planning. This is a high-priority feature for myself and the rest of the engineering leadership team.
Do you have a timeline for when this might move into Beta, or will there be another round of EAP invites? thanks
ALM/Rally provides a very simple and intuitive UI for individual-level capacity planning. Once a team is selected, resources are automatically populated based on the onboarding already done in ALM. A similar capability exists in Jira as well, where navigating to a space shows a Capacity tab and allows adding people directly.
In ALM, capacity can be entered in hours at the individual level. After entering the capacity, ALM automatically pulls the task data for the selected sprint and shows the workload. For example, if Tom’s capacity for Sprint 3 is set to 40 hours and he has tasks totaling 45 hours in that sprint, ALM clearly shows his load as (45/40) × 100, i.e., ~110% utilization for Sprint 3.
In contrast, capacity planning in Jira is unnecessarily complex. We are required to enter hours, days, or percentages for every week and against individual work items. This approach is cumbersome, unintuitive, and adds significant overhead without clear value.
A much simpler solution already exists conceptually in Jira through the Plans tab, where team capacity can be entered at the sprint level and we can see the team loading for a particular sprint. Jira could easily extend this capability to show all work assigned to the team for that sprint and automatically calculate individual and team-level loading. Since teams and team members are already defined in Plans, this would have been a far more straightforward and scalable implementation.
I strongly recommend simplifying Jira’s capacity planning by aligning it with the ALM/Rally model or by extending the existing Plans functionality to support sprint-level capacity planning and workload visibility.
Looking forward to a positive response and an improved experience in this area.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Excited to see this feature! A few things others have raised that we'd strongly echo:
+1 on Story-level support and having more ways to measure — Epic-only is limiting for teams doing detailed capacity planning, and ideally capacity would be based on story points available, not just the count of work items assigned
Also +1 on making this available in Plans and custom filters for cross-space visibility — many of our people work across multiple spaces run by different PMs and a single consolidated view is essential
We'd love to be included if another EAP round opens up!
Two additional questions from our team as we think through how this would work in practice:
Workload source beyond Assignee
Will workload calculation be limited to the Assignee field, or will there be support for other user fields (e.g. Reviewer, QA Owner, or custom user-picker fields)?
In many workflows, the person doing the work isn’t always the Assignee — it’d be great to configure which field(s) drive capacity and/or some kind of weighting as to what those user fields signal.
Excluding stalled/blocked issues from active workload
Will there be a way to exclude issues in certain statuses (e.g. Blocked, On Hold) from counting toward a person’s workload?
Someone can be “assigned” to 10 epics but if 7 are blocked, their real capacity is very different — the current model could significantly overstate how loaded someone is.
Where do we see the latest updates for the EAP and information on the functions? I was expecting to see it here on the community page but we notice updates in Jira first. It would be helpful so we can communicate it through to our delivery team.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 31, 2026 edited
Hi, I’m Anukrati! I’ve recently taken over as the Product Manager for Jira's Individual Capacity Planning.
First off, I want to thank you all for the enthusiasm and the thoughtful feedback, we hear you!
These are all valid and important asks, whether it’s capacity planning across levels from budget through to execution, integration with plans, auto-calculation of utilisation from sprint tasks, or story-level support. Such broader, multi-level scenarios are being considered at a strategic level to power a holistic solution, and you’ll hear more as plans progress.
That said, ICP’s MVP does not aim to solve strategic or detailed workload scenarios today. Our experience focuses on one specific part — helping people managers, team leads and project managers plan individual capacity against big rocks of work over a quarter or more directly in Jira. Our main goal is to materially reduce the need for you to juggle spreadsheets and other tools to get this done!
Furthermore, I want to share that we have made improvements to the experience recently and are gearing up for more! Here’s a sneak peek of what’s available and what’s coming:
What’s new
You can now plan contributions in %ge or hours or days for greater flexibility.
Update multiple cells quickly with multi-select, copy/paste, and autofill.
Focus your view by contributor, work item, work type and status filters.
Easily visualise resourcing against Big rocks of work with a Work-first view.
What’s coming up
Capability to reorder contributions for easy maintenance.
Better relevance of people/work suggestions to speed up setup.
Capability to add contributions against Atlassian Projects.
AI-assisted setup to let you import spreadsheets to bootstrap from existing data.
AI-assisted maintenance via a Rovo skill to let you manage capacity with natural language.
Get involved
If you haven’t been enabled for the EAP due to high demand, watch this space for announcements on Beta timelines and future feature updates. Meanwhile, keep the feedback coming—what works, what’s missing, and what you want next. Your inputs are invaluable in shaping this early version!
"That said, ICP’s MVP does not aim to solve strategic or detailed workload scenarios today. Our experience focuses on one specific part — helping people managers, team leads and project managers plan individual capacity against big rocks of work over a quarter or more directly in Jira"
I don't think this will help people managers since they will not see the full picture of the people they manage in project or product spaces.
Will this view be available for multiple projects as boards can, or is it restricted to a single Jira space like the timeline has been?
If you can use this with multiple Jira spaces, then you can create a board with a filter for all users you manage, and that could give you an overview of your people. As long as the percentages are based on total available time for the individuals, that could work. It demands that you can set absences and holidays, but I think that is included?
If you can't use this view with multiple Jira Spaces, then it will be of limited use for people managers, but still a useful planning tool for Teams, assuming they take the time to do the planning that is.
btw, is this in any way connected to the estimations, or can I add any number I want without any indication if it is beyond what has been estimated?
...and congratulations on the new position @Anukrati Saxena ! We look forward to hearing more about the future of this feature, and the bigger feature you hinted towards ;)
@Anukrati Saxena Congratulations! We're very excited to get access to this functionality - and all of the changes (especially options over hours vs. estimates) look great.
@__ Jimi Wikman I've asked the question before - and cross-team planning may actually work by creating a new Portfolio Jira space that brings bigger work items (Epics and above?) together from other Jira spaces - and hopefully groupable by Team!
For example, a new filter could be created using a query like this:
issuetype in (Initiative, Epic) and project in (TEAM-1, TEAM-2, TEAM-3)
This should enable the board/capacity planning to see work across teams.
Because I agree - if we can't run capacity planning for people who work across multiple Jira spaces - this will have limited scope until it goes the level above.
35 comments