Configuration Change Volume Over Time(4.4.6)

Configuration churn, meaning frequent changes to issue types, fields, boards, and workflow definitions, changes what your historical metrics mean: numbers computed before and after a schema change may not compare the same things. This visual counts genuine configuration changes so you can see when your site's structure actually moved.

What you can conclude

• A cluster of configuration changes in one week usually corresponds to a planned admin session, a new project setup, or a schema migration; if nobody recognizes it, that is worth asking about.
• A steady trickle of changes week after week means the site's structure is evolving continuously, and historical comparisons should be read with that in mind.
• A true zero week means we observed your event stream and saw no configuration activity, which is different from a week with no data at all.

What counts as a configuration change

Issue type, field, and field-context changes; project creations, updates, and deletions; components and filters; board configuration; and workflow definition changes. Ordinary delivery activity, such as resolving issues, editing descriptions, moving items between sprints, or attaching files, does not count.

How this chart works

Weekly site-wide counts with a category split and a 4-week moving average. The date filter selects which weeks are shown.

The week in progress is shown at its raw count so far. Because the week is not yet complete, it carries no week-over-week change and does not enter the moving average.