Configuration Event Type Distribution(2.2.5)

Every time someone adds a field, changes an issue type, modifies a project setting, or changes a user account, it generates a configuration event. This visual shows the breakdown of those events by category — giving an at-a-glance view of where your Jira configuration is evolving.

Most configuration activity is legitimate. But when one category spikes unexpectedly — especially field creation or user changes — it can indicate unplanned schema growth, permission creep, or changes outside an approved window.

What you can conclude

• A spike in field or issue-type creation suggests schema growth that may not have been planned — raising the governance and audit surface.
• A high volume of user events outside of known onboarding cycles may be worth cross-checking with HR records.
• A balanced, low-volume distribution across all categories means few configuration changes were recorded and no category dominates.

How this chart works

Horizontal bar chart showing the count of all admin-level configuration events grouped into one bar per domain: Field, Field Context, Issue Type, Project, Component, Filter, Board, Workflow, and User. A configuration change of a kind not listed here appears under its own name rather than being left out. Each bar carries the first and last seen timestamps for that domain. This chart is not bound to the date filter: the counts cover the whole recorded history, so they can total more than the date-filtered cards on the same page.