A simple team capacity & workload heatmap on any Jira dashboard — one color-coded bar per person, straight from the estimates your board already has. No setup, no bloat.
Free for up to 10 users · No re-entering estimates · Read-only, runs on Atlassian
One glance shows who is overloaded, near capacity, on track or free — plus team totals and CSV export.
Standups & spreadsheets vs this gadget
| Without this app | Team Capacity for Jira |
|---|---|
| ✕ Overload surfaces mid-sprint, once it's already too late | See who's overloaded on the dashboard, before you commit |
| ✕ Capacity lives in a side spreadsheet nobody keeps current | Uses the estimates your board already has — nothing to re-enter |
| ✕ Heavy PPM / resource suites need admin setup and a per-seat budget | One gadget, any user, set up in 30 seconds |
| ✕ “Everyone has the same capacity” ignores part-timers and vacation | Per-person capacity overrides and custom thresholds PRO |
| ✕ No shared record for the retro or stakeholders | CSV export: estimate vs actual per person PRO |
| ✕ Data leaves your site to a vendor's servers | Runs on Atlassian — read-only, zero external egress |
Deliberately one screen and no wizard — a sprint workload balancer, not a portfolio/PPM suite. It answers one question fast: can my team actually take this on? See how workload is measured →
Set one default capacity for the team, then override individuals where reality differs: someone at 60 %, a new joiner ramping up, a colleague on vacation this sprint. Blank means “use the default”.
The thresholds are yours too — decide where near capacity and overloaded begin. Set up in about 30 seconds, on one small form.
Built to fit how your team already works
Workload comes from the estimation your board already uses — Story Points, time estimates (auto-converted to hours), or plain issue count for teams that don't estimate.
Company-managed and team-managed Scrum boards both work, including the team-managed Story point estimate field. You only ever see boards you have permission to browse.
Strictly read-only and built on Atlassian Forge with zero external egress. Every viewer's Jira permissions are enforced server-side on every request — your data never leaves Atlassian.
Also included
Estimate vs actual PRO
One click exports load, capacity, utilization %, status, issue counts and time spent per person — straight into Excel or Google Sheets.
Setup
Install from the Marketplace, open a Jira dashboard, choose Add gadget and search for “Team Capacity”.
Choose a Scrum board, how to measure workload, and a default capacity per person. Save.
The color-coded bars render immediately and refresh automatically — switch sprints right in the header.
FAQ
Add the Team Capacity gadget to any Jira dashboard, pick a Scrum board and set a capacity per person. You get a color-coded workload bar per assignee for the current sprint — red means overloaded, amber near capacity, green on track, blue free capacity. See the 30-second setup guide.
No. Team Capacity measures workload the way your board already estimates: Story Points, time estimates (auto-converted to hours) or plain issue count. Nothing to re-enter, nothing to sync. If your issues carry no estimates yet, switch Measure workload by to issue count.
Yes — company-managed and team-managed Scrum boards, including the team-managed Story point estimate field. Kanban (date-window) support is on the roadmap.
Yes — with Pro you override the default capacity per person: part-timers, new joiners, vacation weeks, on-call rotations. The free plan uses one default capacity for everyone. Pro also lets you count only unfinished work and set custom thresholds.
Free for teams of up to 10 users — the full workload heatmap on any Scrum board. Pro adds per-person capacity, remaining-load mode, custom thresholds and CSV export (estimate vs actual per person). Larger teams get a free trial; see the Marketplace listing for per-user pricing.
Also from Janek Behrens
Free for up to 10 users — the workload heatmap on your dashboard, in minutes.
