Capacity Planning with PTO & Holidays: How It Works
Key Takeaways
Release Management, Roadmaps & Product Portfolio for Jira subtracts weekends, applicable public holidays, and individual PTO from calendar days so its Monte Carlo forecast uses the team's real availability instead of assuming every day is a working day.
PTO is recorded against the actual Jira user accounts assigned to issues, so a person's availability drops only on the specific days they are away rather than applying a blanket percentage to the whole team.
Public holidays can be imported in bulk from a CSV file and applied per team, and teams in different countries can carry different holiday calendars at the same time.
Accounting for non-working days bends the burnup chart where the team is actually out and shifts the p50, p85, and p95 release dates to match, because PTO and holidays remove specific people on specific days.
When resource availability changes after a release is committed (leave approved later, a holiday calendar loaded for a team that joined, a departure recorded as time off), the committed date is re-forecast and the shift is reported in days against the P50/P85/P95 bands. The app does not store allocation percentages or skills and is not an HR system.
Capacity and forecasting run natively inside Jira Cloud on Atlassian Forge, with no data exported to an external service to perform the calculation.
This page explains how Release Management, Roadmaps & Product Portfolio for Jira accounts for paid time off (PTO) and public holidays when calculating team capacity and forecasting release dates. It is a neutral, factual reference for how the capability works. Companion article: Resource Availability Is Confirmed at the Vote. It Changes the Week After.
Why non-working days matter to a forecast
A release forecast is only as accurate as the capacity it assumes. If the model treats every calendar day as a working day, it overstates how much the team can complete and pulls the projected release date earlier than the calendar can support. PTO and public holidays are the most common reason a fully planned sprint or release slips, because they remove specific people on specific days rather than reducing the whole team evenly.
Tying PTO to real Jira users
PTO is recorded against the actual Jira user accounts on the team, the same accounts assigned to issues. When a person is marked as out, their availability is reduced only on the days they are away, so the capacity calculation reflects who is absent and when, not a blanket percentage applied to the whole team.
Importing public holidays in bulk
CSV import: a set of public holidays can be loaded from a CSV file rather than entered one date at a time.
Per-team application: an imported holiday set is applied to the relevant team, so those dates are treated as non-working days for everyone it covers.
Multiple regions: teams distributed across countries can carry different holiday calendars at the same time, and the plan respects each.
How capacity feeds the forecast
Working days are calculated as calendar days minus weekends, applicable public holidays, and individual PTO. That adjusted capacity is what the Monte Carlo forecast uses when it simulates how long the remaining scope will take. As a result, the p50/p85/p95 release dates reflect the team's real availability, and the burnup chart bends where the team is actually out instead of following a uniform slope.
Capacity adjustments are inputs to a probabilistic forecast, not a guarantee. They make time off visible so scope, capacity, and date can be traded off deliberately.
Resource availability after the commitment
Resource availability (who can work on the release, on which days, after leave and holidays) is usually confirmed when the team commits to a release date, for example at a PI planning confidence vote. That confirmation is the team's judgment and the app does not replace it. After the commitment, availability can change without any change to the release's scope. The table shows how each kind of change reaches the forecast.
Availability change after the commitment | How it reaches the forecast |
|---|---|
Leave approved after the commitment | Read directly once recorded as PTO against the person's Jira account for the days concerned. |
Team or region joining with its own public holidays | Read directly once its holiday calendar is imported (CSV) and applied to that team. |
Departure (resignation, end of contract) | Read directly if the days after the person's last day are recorded as time off against their account; otherwise registered through delivered throughput as the affected work slows. |
Loan or pull-away for a known period | Read directly if recorded as time off for the days concerned; otherwise registered through delivered throughput. |
New member ramping up | Not read as availability. Completed work enters the throughput history as it is delivered. |
Allocation percentages, skills | Not read. The app does not store allocation percentages or skills and is not an HR system. |
Procedure:
At commitment, record the committed date and the confidence level the team committed at, alongside the availability the team confirmed.
When availability changes, record it (PTO, holiday calendar, time off for a departure or loan) before it takes effect, then read the re-forecast.
At each sprint or iteration boundary, read the gap in days between the committed date and the forecast at the committed confidence.
The committed date is carried with its confidence across the P50, P85, and P95 bands. A release is on-track when the committed date sits on or after P85, amber between P50 and P85, and at-risk below P50. For how the app treats unplanned capacity change more broadly, see Capacity Change Tracking & the Committed Release Date: How It Works.
Where it runs
Capacity and forecasting run natively inside Jira Cloud on Atlassian Forge. No data is exported to an external service to perform the calculation.
Related
Resource Availability Is Confirmed at the Vote. It Changes the Week After. (divim.io)
The three things that erode a committed release date (divim.io)
Capacity Change Tracking & the Committed Release Date: How It Works
Release Management, Roadmaps & Product Portfolio for Jira on the Atlassian Marketplace