JIRA HEALTH CHECK — 25-POINT REVIEW
Devendrappa | Jira Implementation Specialist

CONFIGURATION
[ ] Issue types and hierarchy are appropriate
[ ] Workflows match the actual business process
[ ] Statuses are meaningful and not duplicated
[ ] Screens expose only relevant fields
[ ] Custom fields are necessary and clearly named
[ ] Permission schemes follow least privilege
[ ] Notification schemes are intentional
[ ] Issue security is configured where required

DELIVERY & REPORTING
[ ] Boards have clear filters and ownership
[ ] JQL filters are reusable and documented
[ ] Dashboards match stakeholder needs
[ ] Sprint/project/leadership metrics are defined
[ ] Aging, throughput or cycle-time views are available where useful
[ ] Backlog and issue data are clean enough for reporting

AUTOMATION
[ ] Automation rules have clear names and owners
[ ] Obsolete/duplicate rules are removed
[ ] Rules do not create loops or conflicting updates
[ ] Smart values and conditions are documented
[ ] Notifications are limited to useful events

GOVERNANCE
[ ] Project and configuration ownership is defined
[ ] Naming conventions are documented
[ ] Changes have a lightweight approval/change process
[ ] Admin documentation is current
[ ] User/admin training and handover are available

RECOMMENDATION
Classify findings as: Critical / High / Medium / Low.
For each finding record: Current State | Risk | Recommendation | Priority | Owner | Target Date.