The resource view at the vote had one red cell. Priya was assigned 130% in sprint four: the payments work plus the data migration. The team spent twenty minutes on it. The migration moved to a second developer, the cell turned green, and everyone voted four fingers.
Three weeks later the second developer was pulled onto an incident, and the migration quietly went back to Priya. Nobody reopened the resource view, so the cell stayed green. The release finished five days past its committed date. (A composite, not a customer.) The overallocation had never been removed. It had been moved, and then it came back.
What overallocation is
Overallocation means a person, or a role, is assigned more work than their available time covers. In a resource plan it shows as anything above 100% for a period. Spotting it at planning is good engineering judgment, and the fix the team chooses (move the work, delay it, add someone) is part of the evidence behind the confidence vote.
Jira itself does not hold an allocation percentage. The assignee field says who owns an issue, not how many other issues, other projects and other commitments sit on the same person. So overallocation lives in a spreadsheet, a capacity template or a planner’s head, and it is checked about as often as that document is opened.
Cleared at planning, back after the vote
An overload that is resolved on paper tends to return in four ways:
- The fix moved the load. Shifting the work to someone else only works while that person stays free. When they are pulled away, the load returns to its first owner.
- Loans and pull-aways. An audit, an escalation or another team’s deadline takes days from people the plan counted as fully on the release.
- New asks land on the same person. Added scope rarely spreads evenly. It goes to whoever knows the area, which is usually the person who was already full.
- Overloaded people queue work. Work in progress rises, reviews wait, and completed work per sprint falls even though everyone is busy.
None of these adds a ticket to the release or changes the headcount. The resource view can stay green while delivery slows. That is a capacity change landing after the vote, the third of the three things that erode a committed release date, and it often arrives with scope creep, because the new ask is what overloaded the person.
Keep the judgment. Read the effect in days.
The answer is not to stop checking for overallocation. It is to read what an overload costs the date after the vote, not only whether the cell is red on planning day.
- At planning, write down the overallocation you found and how you resolved it, next to the committed date and the confidence level the team voted at.
- When a known pull-away or loan starts, record the affected days as time off against that person’s Jira account before it starts.
- Keep the assignee on each issue honest. If the work has moved back to the first owner, reassign it in Jira.
- At every sprint boundary, read the gap in days between the committed date and the forecast at the committed confidence, instead of re-reading the allocation sheet.
An illustration, not customer data. A release is committed for 26 June at 85% confidence. At the vote the 85% forecast sits at 22 June: four days of margin. In week three a migration returns to a developer already carrying the payments work, and a second developer is pulled onto an audit for four days. No issues were added. The 85% forecast moves to 1 July, five days past the commitment. The 50% forecast is 25 June, so the release reads amber (attention), not yet red.
Now the sync has a decision with a number on it. Move the audit support to someone else? Cut the lowest MoSCoW item? Renegotiate the date while there is still margin to trade? Each option is the team’s call, and so is every assumption behind the forecast. What changes is that the call happens in week three, not at the release demo.
Where Advanced Release Planning fits
Advanced Release Planning for Jira does not store allocation percentages and does not flag an overallocated person. It reads what overallocation turns into: time off recorded per person against the Jira accounts assigned to issues, holiday calendars imported per team, and the team’s delivered throughput and work in progress. The Capacity Awareness setting folds that availability into the Monte Carlo simulation, so when a pull-away is recorded, or slower delivery shows up in throughput, the committed date is re-forecast and the shift is reported in days. The committed date carries its confidence band (50%, 85%, 95%) and stays current as scope, dependencies and capacity move. The team sets the assumptions: which throughput window, whose capacity, what is in scope. The app does the arithmetic at Monte Carlo scale and keeps it live. Green at or above P85, amber between P50 and P85, red below P50.
Overallocation is usually resolved by leveling; see what resource leveling does to a committed release date, and what a resource histogram can and cannot tell you after the vote. For the percentage view of the same problem, see resource utilization in days. For exactly what the app reads, see the capacity change tracking reference doc.
Key takeaways
- Overallocation means more work assigned than available time. Resolving it at planning is expert judgment and part of the confidence vote.
- After the vote it returns through moved loads, loans, new asks on the same person and queued work, without adding a ticket or changing headcount.
- Jira holds no allocation percentage. Record known pull-aways as time off against the person’s account and keep assignees current.
- Read the gap in days between the committed date and the forecast at the committed confidence at every sprint boundary.
FAQ
What is overallocation in project management?
Overallocation is when a person or role is assigned more work than their available time covers in a period. In a resource plan it appears as an allocation above 100%.
What is the difference between overallocation and overutilization?
Overallocation is about assignments: more work planned than time available. Utilization is about time actually spent against available time. A person can be overallocated on the plan while the utilization report still looks normal.
How do you track overallocation in Jira?
Jira has no allocation percentage. Keep assignees accurate, record known loans and pull-aways as time off against the person’s account, and read the committed date and its confidence band for the effect on delivery.
Clear the overload. Then keep the date honest. See the committed date and its live confidence band in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




1 Comment
Leave your reply.