Jira Health Score
66
/ 100
Needs attention
↑ 6 points since last saved scan
Critical
0
Warnings
2
Info
1
See Jira configuration health at a glance
This demo uses static sample data for Acme Engineering. Connect your own Jira Cloud site to run live scans. Read-only monitoring for Jira Cloud.
Priority findings
Configuration risks detected in the demo site.
warningCustom Fields
Elevated custom field count
Your site has a high number of custom fields, which can increase admin overhead and slow configuration reviews.
Evidence
458 custom fields detected
Affected objects
458
warningWorkflows
Elevated workflow count
Many workflows can indicate duplication and make change management harder across projects.
Evidence
142 workflows detected
Affected objects
142
infoProjects
Many inactive projects detected
Several projects show no recent issue activity and may be candidates for review.
Evidence
31 projects with no issue updates in 90+ days
Affected objects
31
Health trend
How configuration health changes across saved scans.
warningCustom Fields
Example investigation
Elevated custom field count
458 custom fields were detected across your Jira site. High field counts often correlate with slower admin workflows, harder reporting, and duplicate naming patterns.
Custom fields
458
System fields
112
- Export a custom field inventory and identify unused or duplicate fields.
- Review field contexts tied to a single project versus global contexts.
- Archive or consolidate fields that no longer serve active workflows.
Remediation plan
Example remediation plan
Reduce custom field sprawl
1 / 4 actions completed · In progress
- Export custom field inventory from Jira admin
- Identify duplicate field names and contexts
- Review fields unused in the last 12 months
- Document consolidation plan for stakeholders
Recommendations are tracked in CFGORA. Jira is never modified automatically.
Ready to scan your Jira site?
Connect through secure Atlassian OAuth. Read-only analysis — Jira is never modified automatically.