Project Configuration Mutation Log(2.6.10)

Schema governance events are not evenly distributed across projects. Some projects are heavily customized and see frequent field and issue type changes. Others are stable. This view shows you which projects are accumulating the most configuration changes — so you can identify where schema governance is weakest.

Projects with high field-change counts may be accumulating custom fields faster than they are being retired. If your organization documents configuration changes for a DORA or NIS2 review, this table shows where that burden concentrates, and is the starting point for a targeted schema review.

What you can conclude

• Projects with disproportionately high field or issue type change counts are candidates for a schema review.
• The Global row (events not tied to a specific project) typically represents bulk migrations or system-level changes — worth understanding before dismissing.
• A project with exclusively project-level mutation events (no field or issue type changes) may have permission structure instability rather than schema sprawl.

How this chart works

Sortable data table showing schema change events aggregated by project key. Columns: Project Key, Field Changes, Issue Type Changes, Project-level Events, Total. The Global row captures events with no project scope.