Saved Reports
Saved reports let you keep repeatable report setups without rebuilding the same source, columns, filters, calendar, and chart settings each time.
A saved report stores configuration, not a permanent copy of every calculated result. Rerunning a saved report may reflect updated Jira data.
When to use this
Use saved reports for recurring delivery reviews, weekly bottleneck checks, support queue analysis, or any report setup your team repeats.
Before you begin
- Configure a report that returns the expected result.
- Confirm scope, report type, selected fields, and time settings.
- Choose a clear name that other users can understand.
Steps
- Configure and run a report.
- Open the saved reports menu.
- Save the current report configuration.
- Name the saved report.
- Restore the saved report later when you need the same setup.
- Set a default report if you want StatusPath Reports to open with a preferred configuration.
Result
You can restore saved configurations, continue from recent setups, use draft configurations, and set a default report for faster access.
Notes
Saved report features may include:
- Save report
- Restore report
- Set default report
- Recent configuration
- Draft configuration
- Rename or delete report
- Copy report
A saved report stores the report type, source configuration, Work item range, Trim History, duration format, work schedule, selected columns, dynamic status or assignee columns, groups, sort and filter state, table/chart mode, and chart settings.
The current app enforces a saved report limit of 100 records.
Troubleshooting
If a saved report returns different results later, check whether Jira issues changed, whether permissions changed, whether date range settings are relative, or whether the saved report references deleted Jira filters, removed statuses, unavailable fields, or deleted calendars.