Top Active Custom Fields(5.10.6)

The custom fields receiving the most write activity, ranked descending. Each row shows the human-readable name, the underlying Jira customfield_* id, the field's type, a proportional bar against the busiest field, and the count of edits we have seen. Write counts are measured from the issue changelog; the declared catalog and each field's type come from a daily sweep of the tenant's field list.

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.
• Field types. Each field carries its Jira type where known (for example "Select List (single choice)" or "Date Picker"). Type names are Jira's own wording, exactly as its field administration reports them; fields provided by Jira apps carry their app's type name (for example "Forms" or "Focus Areas"). A type of Unknown means neither the daily sweep nor observed field events could establish it — a statement about our coverage, not about the field.
• 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.

Windows, groups and controls

• Time window. Write counts default to the last 12 months and can be switched to the last 30 or 90 days; the panel states which window is active, and fields whose writes fall entirely outside the selected window are counted in a note beneath the list rather than shown as zero. Per-project counts, the project-filtered ranking, and the last-written dates always use the 12-month total, so the window control is disabled while a project is selected.
• Declared, no writes observed. Fields from the declared catalog with zero recorded writes are listed in their own group beneath the ranked list rather than hidden. The catalog is refreshed daily from the tenant's field list, so it includes fields created before MetaFrazo was installed; a field that was declared and never written is the strongest retirement signal this visual carries. Fields Jira reports as trashed or deleted carry a badge saying so, and each written field shows the date of its last observed write.
• Sorting and filtering. The ranked list can be sorted by writes, last written, number of projects writing, field type, or name, and filtered to a single project or a single field type. With a project selected, ranking follows that project's own 12-month write count, not the tenant-wide total.
• Row bound. The visual reads up to 2,000 fields and states this bound on the page.