Config Stability Score Over Time

Configuration churn — frequent changes to fields, issue types, and workflow settings — is a governance risk. Every change creates inconsistency in historical data, confuses team members, and adds to the audit surface. The config stability score measures how much non-standard field change activity is occurring per project over time — and whether it's getting better or worse.

What you can conclude

• A declining stability score over multiple weeks indicates increasing configuration churn — someone is making frequent changes without a clear governance plan.
• A high, stable stability score indicates a well-governed configuration that changes only when deliberately planned.
• A sudden drop in stability in a specific week may correlate with a schema migration, a new project setup, or an admin session gone wrong — worth investigating.

How this chart works

Multi-line time series showing weekly config stability score per project (0–100). Higher scores indicate fewer non-standard field changes relative to total changelog activity. Use the date and project filters to track specific teams.