Admin-Level Change Events Over Time(2.6.6)

Configuration changes usually follow a predictable rhythm, tied to sprint cycles, project onboarding, or planned migrations. When a week shows an unusual spike, it is either a known event (a schema migration, a new project launch) or something that needs to be explained.

This visual makes the timing of all admin-level activity visible so you can correlate spikes with known events — or flag the ones you cannot explain.

What you can conclude

• For a burst of activity in a single week that does not correspond to a known deployment or migration, a reviewer could ask what change it records and who authorized it.
• Consistent low-level activity spread across all weeks is routine housekeeping.
• A spike dominated by deletion events (field deletions, user removals) removes configuration rather than adding it; the question is whether anything still depended on what was removed.

How this chart works

Weekly stacked bar chart showing admin-level events grouped into four series: user events (blue), field and context changes (amber), issue type changes (purple), and project changes (green). Board and workflow changes are configuration changes and are counted on the Configuration changes page rather than here. Use the date filter to focus on specific periods.

Teams preparing a DORA review commonly use this as the change-activity timeline.

The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes.