CFGORA

Configuration health, continuously monitored.

Keep your Jira environment healthy with automated scans, risk detection, investigations, remediation tracking and change monitoring.

Read-only monitoring for Jira Cloud.

Overview

acme.atlassian.net

Live scan

Jira Health Score

66 / 100

Needs attention

critical

0

Critical

warning

3

Warnings

info

2

Info

Priority findings

warning

Elevated custom field count

458 custom fields detected

warning

Elevated workflow count

142 workflows detected

info

Many inactive projects detected

31 projects with no issue updates in 90+ days

Health trend

↑ 8 since last scan

Product

Monitor the Jira configuration signals that matter

CFGORA focuses on configuration health — the structural signals that often precede workflow issues, admin overhead, and automation fragility.

Configuration Health

Detect configuration growth and potential Jira administration debt before it slows teams down.

Custom Fields

Identify excessive field growth, duplicate naming patterns, and context complexity.

Workflows

Surface workflow proliferation and potential duplication across projects.

Inactive Projects

Find projects that may be candidates for review, consolidation, or archival.

Configuration Activity

Understand recent administrative changes that may correlate with new issues.

API Health

Surface Jira API access and permission problems that affect scan completeness.

How it works

From connection to actionable findings in three steps

1

Connect Jira

Authorize securely through Atlassian OAuth. No Atlassian password is stored.

2

Run a health scan

CFGORA analyses supported Jira configuration and administrative signals for your site.

3

Investigate findings

See evidence, affected Jira objects, recommendations, scan history, and trends.

Actionable findings

More than a score — structured Jira admin investigations

Each finding includes evidence, affected objects where available, and practical next steps. CFGORA helps admins understand what to review, not just that something changed.

warningCustom Fields

Elevated custom field count

Evidence

Custom field count

458

Warning threshold

≥ 300

Why this matters

Configuration growth can increase administration complexity and make Jira harder to maintain, troubleshoot, and automate reliably.

Recommended actions

  • Review unused or redundant custom fields
  • Consolidate similarly named fields
  • Review field contexts
  • Restrict unnecessarily global contexts

Affected objects

Example fields flagged during investigation

FieldSignal
Customer SegmentPossible duplicate
Customer Segment Review
Legacy PriorityNo contexts configured
Sprint Goal CopyGlobal

Read-only recommendations. CFGORA does not modify Jira configuration.

Health history

Track whether your Jira configuration is getting healthier or accumulating risk.

Saved scans let you compare health scores over time and understand what changed between reviews.

  • Saved scan history per Jira site
  • Score changes between scans
  • New, resolved, and severity-shifted findings

Health score trend

72 → 76 → 81 → 78 → 84

Score change

+12

New findings

2

Resolved

4

Severity changes

1 improved

Security

Built for secure, read-only Jira analysis

CFGORA is an independent product and is not affiliated with or endorsed by Atlassian. We describe only security capabilities that are implemented today.

Secure Atlassian OAuth

Connect through Atlassian OAuth 2.0 (3LO). Authorization happens directly with Atlassian.

Refresh-token support

Long-lived connections use refresh tokens so scans can continue without repeated consent.

AES-256-GCM token encryption at rest

Stored OAuth tokens are encrypted before being written to the database.

HTTP-only session cookies

Session cookies are HTTP-only and scoped to reduce exposure in the browser.

Site-isolated scan history

Saved scans and findings are associated with the connected Jira Cloud site.

Read-only recommendations

CFGORA analyses and recommends. It does not modify Jira configuration.

See what's hiding in your Jira configuration.

Connect your Jira Cloud site and run your first health scan.

Read-only monitoring for Jira Cloud.