Quick answer: Jira has limited built-in capacity planning, so most teams add a capacity app from the Atlassian Marketplace or connect a separate resource planning tool. Options include Jira-based apps such as ActivityTimeline, Tempo Capacity Planner and Worklog360, Atlassian’s own Advanced Roadmaps and timeline view, and PSA tools that connect to Jira through an integration. Choose by whether you plan inside Jira or need capacity, time and billing in one system.
Key takeaways
- Jira is strong for issue tracking and sprint planning. Resource planning is fairly limited out of the box.
- There are three routes: use Jira’s own planning features, add a Jira-based capacity app, or connect Jira to a PSA or resource planning tool.
- Jira-based apps keep data in one place. PSA tools add billing, skills and forecasting from sales pipelines.
- Check how a tool reads Jira data (issues, estimates, worklogs) and how often it syncs.
- Plan capacity in hours, not only story points, if you bill for time.
Does Jira have capacity planning?
Partly. Jira’s own features help teams see workload, but most organisations need more for visual scheduling, workload balancing and capacity management.
Atlassian’s own planning features include:
- Advanced Roadmaps (plans): visualise team member workload and capacity during planning.
- Timeline view: shows everyone’s work so deadlines are realistic.
- Rovo in Jira: reviews workloads and helps keep work evenly distributed.
- Confluence capacity planning template: compares each member’s estimated project time with available hours.
Features and plan availability change, so check Atlassian’s current documentation for your Jira edition.
What capacity planning tools work with Jira?
| Tool | Type | What it does |
|---|---|---|
| Advanced Roadmaps and timeline (Atlassian) | Built in | Shows workload and capacity on plans and timelines |
| ActivityTimeline | Jira app | Capacity planning inside Jira using sprint and issue data |
| Tempo Capacity Planner | Jira app | Team and resource management inside Jira |
| Worklog360 | Jira app | Time tracking, resource planning and project financials |
| PSA or resource tools with a Jira connection | External | Capacity, skills, billing and forecasting outside Jira, linked to issues or projects |
App capabilities change, so check each listing on the Atlassian Marketplace before buying.
Which route should you choose?
Route 1: Plan inside Jira
Best for development teams that live in Jira and only need sprint and team capacity. Use Advanced Roadmaps or a capacity app. Keep estimates and worklogs clean, because the plan depends on them.
Route 2: Add a Jira-based resource planning app
Best when you also need scheduling by person, planned versus logged hours and basic budgets. These apps schedule planned hours per person on issues or projects, compare scheduled and logged hours and link plans to rates and budgets.
Route 3: Connect Jira to a PSA or resource planning tool
Best when work spans sales, delivery and finance. The PSA holds availability, skills, forecasts and billing, while Jira holds the technical tasks. You need an integration, so ask how data moves and how conflicts are handled.
How do you do capacity planning with Jira?
- Know available capacity. Account for working hours, leave, public holidays, meetings and internal work. Our guide to what capacity planning is shows the formula.
- Schedule work before it starts. Plan hours per person over a week, month or quarter.
- Spot problems early. Look for overbooked people, empty days and projects competing for the same people.
- Compare planned and logged hours. Check whether estimates are realistic.
- Connect planning to budgets. Track planned revenue, cost and remaining budget.
- Review often. See capacity planning strategies.
What should you check before connecting a capacity tool to Jira?
- Data read: Does it use issues, estimates, story points, worklogs or all four?
- Direction: Is the sync one-way or two-way?
- Frequency: Is it real-time or scheduled?
- Permissions: Does it respect Jira project permissions?
- Setup effort: Who maintains the connection?
- Pricing model: Per Jira user, per planned resource or per tool?
What if your team uses Jira and Salesforce?
Many services firms run development in Jira and sales and delivery in Salesforce. Aprika’s guide to Jira and Salesforce integration covers the pros and cons of connecting them directly, and describes using Mission Control to manage projects inside Salesforce instead. For teams that depend on Jira for development, it also describes linking Jira, Mission Control and Salesforce, and notes the extra complexity, resourcing and training that brings.
Mission Control is a Salesforce-native resource management app with a Scheduler, Resource Planner, Role Forecasting, skills and a Role Utilization Report. Aprika’s Jira guide does not describe a native Jira connector, so confirm your integration approach with Aprika.
What is the difference between sprint capacity and resource capacity?
- Sprint capacity is how much work a team can finish in one sprint, usually estimated in story points or hours after removing leave and meetings.
- Resource capacity is how many hours each person has across all projects, which matters when people split time between teams or clients.
Sprint tools answer “what fits in this sprint”. Resource planning answers “who is free next month, for which skill”. Teams that bill for time or share people across projects need the second view.
Example: planning a quarter in Jira
A software services team of eight uses Jira for delivery. For the next quarter, the team lead:
- Lists available hours per person after leave and holidays.
- Adds planned hours to epics and issues.
- Checks the plan for overbooked people and empty weeks.
- Compares planned and logged hours at the end of each month.
- Moves work or adds contractors when the plan runs over.
The same steps work in a Jira app or a separate tool. What matters is that estimates and worklogs are kept up to date, because the plan reads them.
What common mistakes should you avoid?
- Using story points to plan billable capacity.
- Ignoring non-project time.
- Letting estimates go stale.
- Planning only inside one Jira project when people work across several.
- Buying a tool before deciding whether billing and forecasting matter.
Frequently asked questions
What capacity planning tools integrate with Jira?
Jira apps such as ActivityTimeline, Tempo Capacity Planner and Worklog360, Atlassian’s Advanced Roadmaps and timeline, and external PSA or resource planning tools that connect to Jira.
Does Jira have capacity planning?
Jira has limited built-in resource planning. Advanced Roadmaps and the timeline view help with workload, but many teams add an app for scheduling and capacity management.
How do you plan capacity in Jira?
Work out available hours per person, schedule planned hours on issues or projects, check for overbooked people, and compare planned with logged hours.
Can I plan capacity in story points?
Yes for sprint capacity. If you bill for time or staff across projects, plan in hours as well.
Should I use a Jira app or a separate tool?
Use a Jira app if you only plan inside Jira. Use a separate PSA or resource tool if you need skills, sales forecasts, billing and reporting outside Jira.
Can Mission Control integrate with Jira?
Aprika’s guide describes linking Jira, Mission Control and Salesforce, but does not describe a native Jira connector. Confirm the options with Aprika before you plan around it.
Which tool is best for agency teams that use Jira?
See the best capacity planning tool for agencies.
What is the best capacity planning app for Jira?
It depends on whether you plan only inside Jira or also need billing and forecasting. Compare Jira-based apps and connected PSA tools against your own scenarios.
Do I need Jira Advanced Roadmaps for capacity planning?
It helps with workload and capacity views on plans. Check Atlassian’s documentation for what your Jira edition includes.
Summary
Jira handles issues and sprints well but needs help for full capacity planning. Use Atlassian’s planning features for simple needs, add a Jira-based app for scheduling and hours, or connect a PSA when capacity must link to skills, forecasts and billing. Check how data syncs before you commit.
