Top Active Custom Fields

The custom fields receiving the most write activity in the last twelve months, ranked descending. Each row shows the human-readable name, the underlying Jira customfield_* id, a proportional bar against the busiest field, and the count of edits we have seen. The list is sourced from the issue changelog, not from a static field catalog.

What you can conclude

• Distribution shape. A few fields doing most of the work is the normal pattern; a long tail of fields with single-digit activity is clutter that slows down screens, search, and audits.
• High-activity fields need careful change management. Renames, type changes, or context changes on a busy field have outsized blast radius — automations, dashboards, and integrations are likely tied to it.
• Low-activity fields with generic or test-like names are retirement candidates. Names like "TDG 605 Field", "Untitled", or "Field (updated)" are tell-tale signs of leftover work.
• Coverage caveat — read with this in mind. The catalog is complete from the date the connector was installed forward. Create-and-forget fields (set on issue creation but never edited) won't appear here even if they exist in the tenant.
• Where the activity lives. Each field also lists the projects ("spaces") that wrote it most — the busiest few as KEY · count tags with a "+N more" rollup — so you can tell a tenant-wide field from one driven by a single team, and aim any clean-up at the right project.