User Guide
Saved Plans
"Saved Plans" is no longer a separate sidebar section - saving and reloading a plan both happen from the same Capacity Planner & Insights → Planner screen.
What Gets Saved
When you save a Capacity Planner configuration, the following is preserved:
| Saved | Not Saved |
|---|---|
| Selected groups / teams | Live Jira worklog data |
| Date range | Current issue statuses |
| View mode (Days/Weeks/Months) | Hours that have changed since last save |
| Grouping configuration | New issues assigned after save |
Opening a saved plan re-runs the query against current Jira data - it always shows live data within the saved scope.
Saving a Plan
- Configure the Capacity Planner (groups/teams, date range, grouping, view mode)
- Click Save in the top-right toolbar
- Enter a descriptive plan name (e.g., "Q2 Sprint 5 - Platform Team")
- Click Confirm
Loading a Saved Plan
- From Planner, open any previously saved plan from the list on the landing page
- The planner reloads with the saved configuration and current Jira data
Naming Convention Tips
Use a consistent naming pattern to keep saved plans organised:
[Team] - [Sprint/Quarter]- e.g., "Backend Team - Sprint 10"[Date] - [Purpose]- e.g., "2025-Q3 Capacity Review"[Program] - [PI Number]- e.g., "Engineering - PI-2025-Q2"
Tips
- Save a plan at the start of each sprint to capture the initial commitment baseline
- Don't reconfigure from scratch each sprint - open the previous plan and adjust the date range