Plans, teams and capacity
A plan is a cross-project timeline for people who plan delivery, such as project leads and managers. It gathers work from several places and shows dates, dependencies and capacity. You can try changes in a scenario before anything touches a work item.
A plan needs a signed-in person. API tokens and agent sessions cannot use plans or teams.
Create a plan and choose its sources
Section titled “Create a plan and choose its sources”A plan takes its work from sources: projects, boards and saved filters. You can exclude parts of a source. A plan holds up to 50 sources and up to 5,000 work items that you can currently read. A larger plan answers with an error and never with totals from a cut-off page.
The plan shows only what you may read. A hidden parent, epic or team is removed from what you see, and plan sharing never gives access to the work itself.
Hierarchy and roll-ups
Section titled “Hierarchy and roll-ups”A plan can include levels above epics, such as initiatives. A parent can be in another project if it is exactly one level higher. The plan rolls up dates, progress and estimates from children to parents. Missing values are shown as missing and are never filled in.
Dependencies and warnings
Section titled “Dependencies and warnings”Cross-team dependencies are drawn as links between work. The plan warns about cycles and about dates that contradict a dependency. Warnings also cover missing estimates, over-capacity, overdue work and an inconsistent hierarchy. Each warning rolls up to the items behind it, so you can inspect them.
Teams and capacity
Section titled “Teams and capacity”A team has members. It is either shared across plans or plan-only. A team’s capacity depends on its sprint iteration, velocity and allocation settings. Capacity can be set per sprint or period with holidays, in story points or in time.
Points and seconds are separate units and are never converted into each other. Missing estimates and unknown capacity stay visible. Shared teams survive the deactivation of a member. An owner or administrator can promote a plan-only team to a shared team.
Try a what-if scenario
Section titled “Try a what-if scenario”-
Create a scenario in the plan, or copy an existing one. A scenario starts from a saved baseline of the plan.
-
Propose changes to dates, estimates, sprint, versions, the shared team or the parent. Proposals stay in the scenario and change no work item.
-
Optionally run auto-schedule. Choose which work to plan and how: overwrite existing dates, reschedule future sprints, or finish by release dates. You see a proposal first, and work left without dates is listed with the reason. Accepting it adds the dates to the scenario only.
-
Compare the scenario with its baseline or with another scenario. Items that differ are shown side by side.
-
Review the proposed changes and commit the fields you choose back to the work items.
Auto-schedule is deterministic, so the same input gives the same preview. The schedule horizon is at most 730 days.
Commit chosen fields back
Section titled “Commit chosen fields back”A commit can apply dates, estimates, sprint, fix versions, the shared team and the epic-or-higher parent. It uses the normal rules of each work item: its screens, permissions, workflow and audit. A commit selects at most 100 work items and is applied in one step.
If a work item changed after the scenario was made, the plan marks the proposal as stale. You then keep the proposal or take the current value from the work item. A preview before the commit writes nothing. If only some dates can be applied, the unapplied fields stay pending in the scenario.
Releases
Section titled “Releases”A plan can show release milestones for one project or across projects. It evaluates whether a release is on track and warns about date and scope problems. Scope changes compare the baseline with the scenario, for the work you can see.
Views, presenting and sharing
Section titled “Views, presenting and sharing”You can view a plan as a timeline, a calendar or a summary. Saved views keep grouping, filters, colour rules, zoom and the order of rows, and they can be private or shared with the plan. A view can group work by project, team, status, type, parent or release, and order it by rank, start, due date or key.
Present shows a saved view read-only, with zoom and without editing tools, and you can copy a link to it.
| Sharing | Who can open the plan |
|---|---|
| Private | The owner and eligible site administrators |
| Restricted | People and groups with an explicit grant |
| Public | Signed-in people on your site |
Plan administrators manage sharing. None of these choices bypasses the visibility of the underlying work items.