Admin Ops for Jira
Deutsch Get the app

Clean up Jira custom fields before you reach the limit

The number to reduce is fields that hold no data. The trap is treating “cannot be counted” as “empty”.

The problem

Instances accumulate custom fields for years: one per team, per project, per experiment. Near the 700-field limit, performance and administration suffer, but Jira shows neither how many issues use a field nor which fields duplicate one another.

Step by step

  1. Custom field usage. Scan. Every field gets an issue count, its screens, contexts and a verdict. Expect minutes on a large instance: it is one count query per field.
  2. Duplicate fields. Merge before you delete. Two teams’ “Customer” fields become one, with the values moved across; the source is left empty rather than deleted.
  3. Move to trash. Select the “empty, unused” group only. Every trashed field is restorable for 60 days.
  4. Archive & trash. Note the purge deadline. Nothing in Jira reminds you.

What to watch out for

Fields whose type cannot be queried show as unknown and are never offered for trashing. That is the app declining to guess about data it cannot see.

Start by seeing what your instance is carrying around

The read-only audits work even without a licence. Nothing changes until you decide it should.

Get it on the Marketplace Documentation