User Guide
Saved Plans
Saved Plans let you preserve capacity planner configurations for reuse across sprints, quarters, or recurring planning cycles.
What Gets Saved
When you save a Capacity Planner configuration, the following is preserved:
| Saved | Not Saved |
|---|---|
| Selected users / 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 (users, 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
The plan immediately appears in the Saved Plans section of the sidebar.
Loading a Saved Plan
- In the sidebar, click Saved Plans
- Click any plan name to open it
- The planner reloads with the saved configuration and current Jira data
Managing Saved Plans
| Action | How |
|---|---|
| Rename | Hover the plan → click the Edit (pencil) icon → type new name → Enter |
| Delete | Hover the plan → click the Delete (trash) icon → Confirm |
| Duplicate | Open the plan → modify as needed → Save with a new name |
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 - duplicate the previous plan and adjust the date range