Decision Register Quickstart
Last updated
Run your first Decision Register report and export the results.
Jira administrators
Delivery and governance leads
Decision Register installed and accessible in Jira
Access to target Jira projects
Open Decision Register from the Jira Global Page or Admin Page.
Select one or more projects using search and filter.
Set the time range and max issues scanned.
Optionally filter by issue type and only-my-changes.
Run the register.
Review grouped or table output, counts, metadata, and issue links.
Export to CSV, or use copy-to-clipboard fallback if needed.
Start with one active project where issue history is known.
Use a practical window (for example last 30 days).
Set max issues scanned high enough for useful coverage.
Keep filters light on first run (issue types only, only-my-changes off).
Check grouped/table results before exporting.
Use this setup for a reliable first run.
What the output means:
Each entry shows issue key, summary, when, who, and the from to to change.
Grouped view shows change-type counts; table view is useful for detailed review.
Run metadata confirms scope (project, range, limits) used for that output.
Results include multiple valid change entries with issue links for verification.
Change-type counts and run metadata match your selected scope.
CSV export works, or clipboard fallback is used when download is blocked.
Using a very short time range and assuming no changes exist.
Setting max issues scanned too low for the selected project.
Over-filtering issue types on the first run.
Assuming export writes back to Jira issue data.
No entries found: widen the time range or project selection.
Scan too broad: reduce max issues or narrow issue types.
Clipboard fallback needed: use when CSV download is blocked by local policy.
Last updated
Projects: ENG
Time range: Last 30 days
Max issues scanned: 200
Issue types: Story, Bug
Only my changes: Off
Estimate field: Auto-detect