How to Add Capacity in Jira

Jira is one of the most widely used project management tools in the world — over 65,000 companies rely on it to plan, track, and deliver work. But there’s one feature many teams underuse or skip entirely: capacity planning.

Without it, sprints get overloaded. Deadlines slip. Teams burn out. And the whole point of using a structured tool falls apart.

This guide walks you through exactly how to add capacity in Jira — so your sprints are realistic, your team isn’t overwhelmed, and your work actually gets done on time.

What “Capacity” Means in Jira

In Jira, capacity refers to the total amount of work your team can realistically handle in a given sprint or time period — factoring in availability, working hours, time off, and other commitments.

Jira doesn’t track capacity automatically by default. You have to set it up — either through Advanced Roadmaps (Jira Premium/Enterprise), sprint planning fields, or third-party apps.

Here’s why this matters: research shows that teams who plan with realistic capacity estimates are 40% more likely to complete sprints on time compared to those who rely on guesswork.

Why Teams Skip Capacity Planning (And Regret It)

Most teams skip capacity planning for one of three reasons:

• It feels like extra admin work
• They assume “the team will figure it out”
• They don’t know where to find the feature in Jira

The result? 67% of software teams report that poor sprint planning is the #1 cause of missed deadlines (Atlassian State of Teams Report). That’s not a small number — that’s a majority of teams consistently underperforming because they didn’t take 10 minutes to set capacity.

How to Add Capacity in Jira — Step by Step

Using Advanced Roadmaps (Jira Premium)

Advanced Roadmaps is Jira’s built-in capacity planning tool. Here’s how to use it:

Step 1 — Open Advanced Roadmaps Go to your Jira project → click Plans in the left-hand navigation → select an existing plan or create a new one.

Step 2 — Access the Capacity View Inside your plan, click the Capacity tab at the top. This shows you each team member’s available hours per sprint.

Step 3 — Set Team Member Availability Click on a team member’s name → set their daily hours and working days. If someone is on leave or part-time that sprint, adjust their hours accordingly.

Step 4 — Assign Story Points or Hours to Issues Make sure each issue in your backlog has story points or time estimates assigned. Jira calculates capacity usage based on these values.

Step 5 — Review Capacity Warnings Advanced Roadmaps will flag any sprint where the team is over or under capacity. Red bars mean overloaded. Use this to redistribute work before the sprint starts.

Step 6 — Save and Share the Plan Once capacity is balanced, save the plan. Share it with your team lead or project manager so everyone is aligned before sprint kickoff.

Using Sprint Planning in Jira Software (Standard)

If you’re on Jira Software Standard (without Advanced Roadmaps), you can still manage capacity manually:

Step 1 — Open the Backlog Go to your board → click Backlog in the left-hand panel.

Step 2 — Create or Open a Sprint Click Create Sprint or open an existing one. You’ll see a sprint panel appear at the top of the backlog.

Step 3 — Set Sprint Capacity Manually Jira Standard doesn’t show capacity automatically. Best practice: add a sprint goal or description that notes the total available story points for that sprint (e.g., “Team capacity: 42 points this sprint”).

Step 4 — Drag Issues into the Sprint Drag backlog items into the sprint. Watch the story point total at the top right of the sprint panel — it updates in real time as you add items.

Step 5 — Compare Against Your Team’s Velocity If your team averages 35 story points per sprint (check your Velocity Chart in Reports), don’t add more than that. Keep within ±10% of your historical average.

Step 6 — Start the Sprint Once the total matches your capacity target, click Start Sprint, set the end date, and go.

Adding Capacity Using Team Settings (Advanced Roadmaps)

For teams using Advanced Roadmaps at scale, you can configure capacity at the team level — not just individual level.

Step 1 — Go to Plan Settings Inside your plan → click the gear icon → select Teams.

Step 2 — Add or Edit a Team Click Add Team or select an existing team. You can name the team, assign members, and set a shared weekly capacity (e.g., 40 hours/week per person).

Step 3 — Set Sprints for the Team Under the team settings, configure sprint length (1 week, 2 weeks, etc.) and the start date of each sprint. Jira auto-calculates capacity per sprint based on this.

Step 4 — Apply to Your Plan Save the team settings. Jira will now apply these capacity values across all sprints in your plan. Any overloaded sprints will be flagged automatically.

How to View Capacity Utilization in Jira

Setting capacity is only half the work — you also need to monitor it.

In Advanced Roadmaps:

• Open your plan → click the Capacity view
• The bar chart shows each sprint’s load vs. available capacity
• Hover over a bar to see which issues are consuming the most capacity
• Use the “By Assignee” filter to spot individuals who are overloaded

In Jira Software Reports:

• Go to Reports → Velocity Chart to see how much work your team completed in past sprints
• Use Burndown Charts during active sprints to catch capacity issues early
• If the burndown line is flat or going up, your team is falling behind — usually a capacity issue

According to Atlassian, teams that actively monitor sprint velocity improve delivery predictability by 33% within three sprint cycles. That’s not a minor improvement — it’s the difference between a team that ships and a team that constantly scrambles.

Common Capacity Planning Mistakes to Avoid

Assuming 100% availability Nobody works 8 productive hours every single day. Meetings, reviews, Slack, and unexpected blockers consume 20-30% of most people’s time. Plan for 70-80% capacity as your baseline.

Ignoring time off Holidays, sick days, and personal leave aren’t surprises — they’re facts of life. A team of five loses effective capacity the moment one person is out. Always adjust sprint capacity for known absences before it starts.

Using story points inconsistently If one person’s “3-point story” takes 2 hours and another person’s takes 8 hours, your capacity math breaks down completely. Run regular estimation calibration sessions so the whole team scores consistently.

Never reviewing velocity Teams that never look at their velocity chart keep making the same capacity mistakes sprint after sprint. Check it every sprint retrospective. It takes five minutes and saves days of missed work.

Overloading to “look productive” Cramming 60 points into a 40-point sprint doesn’t make the team look better — it guarantees carryover, frustration, and morale hits. Sustainable pace matters. Studies show teams that operate at 80% capacity or below deliver more total output over time than those consistently maxed out.

Capacity Planning Best Practices

Use your last 3–5 sprints as your baseline Don’t guess. Look at your velocity chart, find your average completed points, and use that as your capacity ceiling.

Build in a buffer Reserve 10-15% of sprint capacity for unplanned work — bugs, urgent requests, and things that always show up. Teams that do this miss fewer deadlines.

Involve the team in estimation Capacity planning works best when the people doing the work estimate it — not just the project manager. Use Planning Poker or T-shirt sizing to get accurate, collaborative estimates.

Review capacity at every sprint planning meeting Before finalizing the sprint, run through who’s available, who’s out, and what the team’s real capacity is. This five-minute check prevents weeks of frustration.

Use dashboards to stay visible Set up a Jira dashboard with your velocity chart, sprint report, and burndown chart visible to the whole team. Transparency creates accountability.

Tools That Extend Jira’s Capacity Planning

Jira’s native tools are solid, but if you need more depth, these integrations extend what’s possible:

Tempo Planner — Adds detailed resource management and visual capacity timelines directly inside Jira.

BigPicture — Portfolio-level planning with capacity heatmaps across multiple teams and projects.

Planyway — Visual calendar and capacity view for teams that prefer timeline-based planning.

Structure for Jira — Hierarchical work breakdown with rollup capacity tracking across epics and sprints.

How Capacity Planning Connects to Team Growth

Here’s something most Jira guides skip entirely: capacity planning isn’t just a project management problem — it’s a growth problem.

When your team is perpetually overloaded, there’s no room to take on new business. Projects slip. Clients churn. And growth stalls — not because of a lack of demand, but because there’s no system in place to handle it.

The best teams solve this in two ways: they plan internal capacity carefully (exactly what this guide covers), and they build predictable external pipelines to fill that capacity with the right work.

That second part — building a pipeline of qualified opportunities that matches your team’s actual delivery capacity — is where most growing teams get stuck. They rely on referrals, inbound, or scattered outreach with no system behind it.

This is where SalesSo comes in.

SalesSo is a done-for-you lead generation engine built specifically for B2B teams. We handle the full outbound system — from precision targeting and campaign design to scaling and optimization — across LinkedIn, cold email, and cold calling. You get qualified meetings booked directly into your calendar, matched to your team’s capacity and growth goals.

No manual prospecting. No guessing. Just a systematic pipeline that works.

Conclusion

Adding capacity in Jira isn’t complicated — but it does require intentional setup. Whether you’re using Advanced Roadmaps for visual planning or managing sprint totals manually in Jira Standard, the principle is the same: match the work to the people, not the wishlist to the calendar.

Start by setting realistic availability for each team member. Use your velocity history as your guide. Build in buffer for the unplanned. And review capacity at every sprint planning session —