Decision Register Configuration
Last updated
Define the run settings and preference controls used to tune register output.
Jira administrators
Governance owners managing report standards
Access to Decision Register page
Project access in Jira
Select projects using search and filter.
Set the time range for the reporting window.
Set max issues scanned for performance and coverage balance.
Filter by issue types where needed.
Toggle only-my-changes for personal activity views.
Configure estimate field handling:
Use auto-detect by default
Set optional customfield override if your estimate field differs
Save and rerun; preferences persist per user in Forge storage.
Use reset-to-defaults when standardising configuration.
Project selection: searchable multi-project scope
Time range: controls event window
Max issues scanned: limits scan size
Issue type filter: narrows scope by issue class
Only-my-changes: returns changes performed by current user
Estimate field mode: auto-detect or explicit override
Preference persistence: Forge storage per user
Overly broad scans can produce partial warnings and slower runs.
Wrong estimate field mapping can hide expected estimate events.
Users may assume shared settings; preferences are per user.
Last updated