Simplify

Workload & Capacity Planner for Jira: Team Heatmap

Workload & Capacity Planner shows who on your team is overloaded, and in which week — estimated hours of each person’s open Jira issues against their weekly capacity. Drag an issue from an overloaded teammate to one with room and it is reassigned in Jira at once.

Capacity heatmap by person and week

People in rows; Overdue, this week, the five weeks ahead and No due date in columns. Each cell holds the remaining (or original) estimate of the person’s open issues due that week: green up to 80 % of capacity, amber up to 100 %, red above. Click a cell to see the issues behind it; set each person’s hours a week in their row.

Rebalance by drag and drop

One column per person — pick people or whole Jira groups — plus Unassigned. Drag an issue to someone else to reassign it, or select several and move them together. Undo is one click (or Ctrl+Z) away.

Across projects and sprints

Plan across all projects or the ones you choose; filter by group, status, issue type, priority or created date. Add a Sprints view (Jira Software), boards by due date, priority, status or any field, save views and share them with everyone.

Also included

  • Column sums — original or remaining estimate, Story Points or any number field per person.
  • Swimlanes — by project, epic, priority or assignee.
  • WIP limits per column, card fields, auto-refresh and due marks on every card.
  • Saved profiles and shared views with links; Export to CSV for planning meetings; a dashboard gadget.

Estimates come from Jira’s time tracking fields; the app does not log time or track leave.

Runs on Atlassian

Workload & Capacity Planner is built on Atlassian Forge. Reassignments are made as you, with your Jira permissions. Profiles, views and capacities are stored inside your Atlassian site; the app makes no external calls. See the privacy policy.

  • Deadline Tracker — every overdue and upcoming deadline on one board.
  • Priority Board — decide what each person tackles first.
  • Kanban Status Board — real workflow transitions with WIP limits and swimlanes.
  • OutSync — leave and out-of-office on your Jira board, synced with Google Calendar.

Capacity looks fine on paper but sprints still slip? Read the ghost resource problem and why HR leave trackers don’t help sprint planning.

Frequently asked questions

Where do the hours in the heatmap come from?

From Jira's time tracking fields — the remaining estimate of each open issue, or the original estimate when nothing remains recorded — counted in the week of the issue's due date.

Can I set a different capacity for each person?

Yes. Click "40h a week" under a name and type their hours (1 to 168). Weeks are green up to 80 % of that capacity, amber up to 100 % and red above.

Does it work across several projects and for whole groups?

Yes. Choose people or Jira groups (every active member is included) and all projects or only the ones you pick.

Does it track time off or log work?

No. It reads estimates and assignments; it does not log time or track leave. For leave, see OutSync, which shows who is out on your Jira board.

Where is my data stored?

Issues stay in Jira. Profiles, views and capacities are stored in the app's Forge storage inside your Atlassian site; nothing is sent outside Atlassian.