Reuse a previous plan
Most sprints look much like the last one: the same people, the same standups, the same refinement session. Capacity Compass can carry those forward so you are not rebuilding the same plan every fortnight.
Before you begin: You need the Administer projects permission, and the project needs at least one existing plan.
Copy a previous plan forward
- Start a new plan as usual and choose the sprint.
- Under Start from a previous plan?, select the plan to copy from.
- Select what to bring across.
- Finish the rest of setup and select Create plan.
What you can bring across
| Option | Copies | On by default |
|---|---|---|
| Members | The people on the previous plan | Yes |
| Meetings & ceremonies | The repeating activities and who attended them | Yes |
| Ad-hoc meetings | The one-off activities | No |
Ad-hoc meetings is off by default because one-offs are specific to the sprint they happened in. Last sprint's conference is not happening again. Turn it on when a one-off genuinely repeats.
What happens to the settings
Choosing a previous plan also carries its estimate settings forward: the estimate field, whether you plan in points or hours, the conversion, and the actual time source. These appear tagged Previous so you can see where each value came from.
A setting only carries forward if it still exists for the board. If a story point scale was deleted since, or a Jira field is no longer available, Capacity Compass falls back to the current board default and tags it Default instead.
The tags are worth reading before you create the plan. They tell you which values you inherited and which ones came from the board.
What is not copied
Individual hours are not copied. Every member starts fresh at the new plan's work days multiplied by its hours per day.
This is deliberate. The new sprint has its own length and its own holidays, so carrying last sprint's adjusted hours forward would quietly import a holiday that has already been taken. Adjust individuals after the plan exists.
Assigned work is not copied either. It always comes from Jira for the sprint being planned.
Clear the selection
Clear the previous plan selection and every field returns to the current board defaults, with Previous tags replaced by Default.