Why field renames are risky
Field names are referenced across filters, dashboards, boards, and automation rules. When the name changes, those assets can silently break and erode trust in Jira reporting.
Checklist before renaming
- Run an impact analysis to list every dependency.
- Classify impacted assets by criticality (SLA, executive dashboards, automated triage).
- Update filters, board queries, and automation rules.
- Save the report and attach it to the change request.
After the change
Validate dashboards with business owners and monitor automation errors for 48 hours. Document any remediation steps in the report library.