Jira Workload Management: Workload by Assignee, Workload Reports, and Balanced Assignment

Does Jira have a workload report?

Not in Jira Cloud, and this is the answer that saves the most time. The reports Atlassian documents for company-managed Cloud projects are the burndown chart, burnup chart, control chart, cumulative flow diagram, epic burndown, epic report, velocity chart, version report, sprint report, cycle time report, deployment frequency report, and release burndown. Every one of them measures the sprint, the epic, or the release. Not one of them breaks work down by the person holding it. If you came here looking for a report called Workload, that is why you could not find it. The three things that do exist are covered below, and none of them is a project report.

How do I see workload by assignee in Jira?

Open the backlog of a company-managed board and look for the Workload by assignee panel. It shows each assignee with the number of work items they hold, the story points on those items, and the remaining time estimate. That is the closest thing Jira Cloud has to a native workload view, and it is enough for a sprint planning conversation. Two things surprise people. The first is that it lives on the board, not in Reports, so anyone looking under the Reports tab will never find it. The second is that it does not exist in team-managed projects at all. If your project was created as team-managed, the panel is simply not there, and no setting turns it on. The options are to move the work to a company-managed project, build the view yourself with JQL, or add a Marketplace app.

The Workload Pie Chart report, and why yours is empty

This is the report most search results are still describing, and it is a Data Center and Server feature. Atlassian documents it as displaying the relative workload for assignees of all issues in a particular project or issue filter, and it has two prerequisites that catch teams out: time tracking must be enabled by an administrator, and the Jira Charting Plugin must be installed. You reach it from the project summary, in the Reports section, then pick the project or filter and the statistic to chart, which is usually Assignee. The reason a Workload Pie Chart comes out blank or lopsided is almost always the time field. The chart totals a time value, not a count of work, so a team that assigns diligently but never fills in an original estimate has nothing to chart. One person who logs hours carefully will appear to hold the entire project. If your team does not estimate in hours, this report will mislead you, and the item count in the backlog panel is the more honest number.

Jira Plans capacity: what Premium buys and what it still assumes

Capacity planning inside Jira Plans is the most complete answer Atlassian sells, and it is gated to Premium and Enterprise. It gives you a People view showing each team member with their allocated work and remaining availability, and a Work view showing which people are allocated to a given project or epic. It also has real prerequisites that are easy to trip over. Work must come from boards: Atlassian states plainly that work drawn from spaces and filters will not show capacity information, so a plan built on a JQL filter shows nothing no matter how the teams are set up. Teams must be linked to a board. Team-managed spaces need sprints enabled. Estimation has to be in story points or hours and days. Then you group by team or sprint and switch on Show capacity on timeline. The assumption worth knowing before you buy the tier is the work week. Each plan is built around a fixed 40 hour work week, and Atlassian documents that custom time-tracking and working-day settings are not yet reflected in these plans. A four day week, a part-time contractor, and a team on a different regional calendar all appear as full-time. Individual allocation also only accepts work at epic level or higher, so day-to-day tickets are not what it is measuring.

Building a Jira workload view with JQL when you have none of the above

If you are on a team-managed project, on a Free or Standard plan, or on Cloud without the Data Center report, JQL plus a spreadsheet gets you a usable workload view in about ten minutes. Filter to the live work rather than everything ever created, along the lines of project = SUP AND assignee IS NOT EMPTY AND statusCategory != Done, then add Assignee, Original Estimate, Time Spent, and Remaining Estimate as columns and export to CSV. A pivot table by assignee gives you the same numbers the paid views would, and it has one advantage over all of them: you choose what counts. Excluding items in a Blocked or Waiting on customer status usually changes the picture more than any other adjustment, because work someone cannot act on is not load. The catch is that it is a snapshot. Nobody re-exports it on a Wednesday afternoon when three tickets land at once, which is exactly when the imbalance actually forms.

Balanced workload in Jira Automation, and where its number comes from

Jira Automation is the one native place where a workload number is used to decide something rather than display it. The Assign issue action offers four methods: a fixed user, round robin, balanced workload, and random. Balanced workload assigns the new work item to whoever currently holds the fewest open work items, which makes it a better default than round robin on most teams. Two limits matter. It counts items, not effort, so a typo fix and a two week migration are the same weight, and on a team where sizes vary wildly the split evens out on paper while the hours do not. And rotation state is tracked per automation rule, not per project or team, so two rules assigning from the same group of people keep separate counters and drift apart. There is also a quiet failure worth checking first: an assignee missing the Assignable User permission is skipped silently, so the rotation looks healthy while excluding somebody. See Jira automation assign issue for the full method comparison.

When measuring workload is not the fix

Every option above answers the same question after the fact: who ended up with too much. That is useful once a sprint. It does not help at four in the afternoon when a spike of requests lands and the person who looks free on Monday morning's chart is now three tickets deep. Balancing at assignment time is a different job, and it is what a routing layer beside Jira does. Assigner reads current open work per person, the skills each item needs, and whether that person is available at all, then hands the work to somebody who can start it and records which rule made the call. It weights by whatever your team uses rather than counting work items, it can see load the person carries outside Jira, and it does not care whether your project is team-managed or company-managed. It is a companion designed to help you decide the assignee rather than a live two-way sync into your Jira site. Pricing is published per user, so the honest comparison is against the Premium tier you may not need yet, not against a number we are ready to charge.

How do I see workload in Jira?

Open the backlog of a company-managed board and use the Workload by assignee panel, which lists each person with their work item count, story points, and remaining time estimate. On Data Center or Server you can also run the Workload Pie Chart report from the project summary. On Premium and Enterprise, Jira Plans shows allocated work against capacity. Team-managed Cloud projects have none of these and need JQL or an app.

Does Jira have a workload report?

Jira Cloud does not. The twelve project reports Atlassian documents cover burndown, burnup, control chart, cumulative flow, epic and release progress, velocity, sprint, cycle time, and deployment frequency, and every one of them measures the sprint or the release rather than the person. The Workload Pie Chart report exists on Data Center and Server only, and needs time tracking plus the Jira Charting Plugin.

Why is Workload by assignee missing from my Jira project?

Almost certainly because the project is team-managed. Atlassian has not brought the Workload by assignee panel to team-managed projects, and there is no setting that enables it. The other common reason is looking in the wrong place: it lives in the backlog of the board, not under the Reports tab, so people on company-managed projects often conclude it is missing when it is one screen away.

What is the Workload Pie Chart in Jira?

It is a Data Center and Server report that shows the relative workload for the assignees of every issue in a project or filter, drawn as a pie. It requires an administrator to enable time tracking and the Jira Charting Plugin to be installed. It charts a time field rather than a count, so on a team that does not estimate in hours it comes out empty or badly skewed toward whoever logs work most carefully.

How do I create a Jira workload dashboard?

Build a JQL filter for live work only, such as work in the project with an assignee and a status category that is not Done, then add dashboard gadgets driven by that filter. A pie chart or two-dimensional filter statistics gadget grouped by assignee gives a workload split, and a filter results gadget with estimate columns gives the detail. Exclude blocked and waiting statuses, since work nobody can act on is not load.

How does Jira balanced workload decide who gets the work item?

It assigns to whoever currently holds the fewest open work items among the eligible assignees you listed in the automation rule. It counts items, not effort or story points, so a one-line change and a two week migration weigh exactly the same. That makes it fairer than round robin on most teams and still blind on a team where item size varies a lot.

Do I need Jira Premium for capacity planning?

For the native capacity view in Jira Plans, yes: Atlassian lists individual capacity planning as a Premium and Enterprise feature. Below that tier the alternatives are the Workload by assignee panel on a company-managed board, a JQL and spreadsheet export, a Marketplace app, or a routing layer that balances work as it arrives instead of reporting on it afterward.

How do I report workload for multiple users in Jira?

Write one JQL filter covering the whole group rather than a filter per person, then group by assignee. Export the result with Assignee, Original Estimate, Time Spent, and Remaining Estimate columns and pivot it, or point a two-dimensional filter statistics gadget at the same filter with assignee on one axis and status or priority on the other. That gives a per-person split without maintaining a dashboard per team member.

What is work ratio in Jira?

Work ratio is the percentage of the original estimate that has already been logged against a work item, calculated as time spent divided by original estimate. It is useful as a JQL condition, for example finding everything over a hundred percent to spot work that blew past its estimate. It is a per-item accuracy measure rather than a workload measure, so it tells you which estimates were wrong, not who is overloaded.

Can Jira warn me when someone is overloaded?

Not natively in a way most teams find useful. The capacity view in Jira Plans shows allocation against a fixed 40 hour week, and it works at epic level or higher, so day-to-day ticket load does not appear. There is no native alert on ticket volume per person. Teams that need this either build a JQL filter with a saved threshold and check it manually, or move the decision upstream and stop assigning to someone once they hit a cap.

How do I set a work in progress limit in Jira?

On a company-managed Kanban board, open board settings, go to Columns, and set a maximum on the column. The column turns red once the number of items exceeds it. It is a visual signal rather than an enforcement: Jira does not stop anyone dragging one more item in. It is also a limit per column rather than per person, so a board can sit inside every column limit while one engineer holds most of the work.

Does Jira Plans capacity respect our working hours and time off?

No. Atlassian documents that each plan is built around a fixed 40 hour work week and that custom time-tracking and working-day settings are not yet reflected in capacity plans. Someone on a four day week, a part-time contractor, and a team on a different regional holiday calendar all appear as fully available. If working hours materially change your capacity numbers, plan around that gap rather than reading the chart literally.