Sample Jira environment

Your Jira health report

See how CFGORA identifies risks, explains evidence, and provides remediation steps.

Sample demo data from a fictional Jira environment. These figures are not real customer metrics.

Health overview

Sample environment · your-company.atlassian.net

Jira health score

0

/ 100

Good

Signals analysed

5

Risks found

3

Recommendations generated

3

Last scan

Today

Risks

Configuration risks worth a Jira administrator's review.

WarningCustom Fields

Elevated custom field count

Why it matters

Your site has a high number of custom fields, which can increase admin overhead and slow configuration reviews.

WarningWorkflows

Elevated workflow count

Why it matters

Many workflows can indicate duplication and make change management harder across projects.

WarningProjects

Many inactive projects detected

Why it matters

Several projects show no recent issue activity and may be candidates for review.

Evidence

Supporting signals for the highlighted finding: Elevated custom field count.

WarningCustom Fields

458 custom fields detected

Affected custom fields

  • Customer Segment · Possible duplicate
  • Legacy Priority · No contexts configured

A large number of custom fields can make administration, search, screens and configuration harder to manage. Duplicate or unused fields also raise the cost of ongoing Jira administration.

Recommendations

Clear remediation guidance your team can act on in Jira.

Recommended action

Review duplicate or unused custom fields and confirm their project/context usage before consolidation.

Steps to resolve

  1. 1

    Export custom field inventory

    Reviewed

  2. 2

    Identify duplicate field names and contexts

    Not reviewed

  3. 3

    Review unused fields

    Not reviewed

Completing work in Jira does not resolve the finding. A later scan can show Resolved · Verified by scan. Until then, completed work stays awaiting scan verification.

Improve your Jira health

CFGORA helps you understand risks and take the right actions to improve your environment.

Before

Jira Health Score

70

/ 100

  • 3 high-risk findings
  • Configuration risks detected
  • Recommendations available

After

Potential improved state

Health score improvement

70 → Improved

  • High-risk findings addressed
  • Risks reduced
  • Jira environment better controlled

CFGORA highlights where improvements can be made and provides guidance to help your team reduce configuration risks.

Example outcome after addressing recommendations. Potential improvement — not a guaranteed score increase.

Sample demo data from a fictional Jira environment. These figures are not real customer metrics.

Ready to check your Jira?

Connect your Jira Cloud site to run a live read-only health scan.

  • Read-only connection
  • No data changes
  • Secure Jira connection

Sample demo data from a fictional Jira environment. These figures are not real customer metrics.