Configscope

Configscope for Jira

The tools on this site do one field at a time, by hand. The app does your whole site — and answers the question cleanup tools skip.

The question other tools do not ask

Every cleanup tool for Jira, including Atlassian's own Site optimizer, decides a custom field is unused by looking at attachment. Atlassian's documentation states the criteria plainly: fields that "aren't in a space or a screen, or have no defined contexts", and on the site-level card, fields that are global and "not associated to any company managed space or screen". Their documentation also notes this is different from identifying fields with no issues.

So a field sitting on twenty screens that nobody has ever filled in counts as used. It will never appear in the list. That is the field you were looking for.

Configscope counts actual values in issues. Both signals matter, and together they sort every field into four cases:

The third row is the one worth pausing on. A field used across many spaces often has no space-specific context — only the global default. Attachment-based criteria read that as "unused" and offer it up. If it holds four thousand values, deleting it destroys four thousand values.

Counting values is not the more thorough test. It is the safer one. Attachment protects your configuration; values protect your data.

Built for Standard plan sites

Atlassian's data limits apply to every plan. The tooling does not: Site optimizer is available on Premium and Enterprise only. That leaves Standard administrators with the constraint and no built-in way to work through it.

Atlassian says as much in its own documentation:

Standard plan users can manage fields by reviewing field usage details in their field configuration schemes and using REST APIs or custom scripts for more detailed audits.

Configscope is that REST audit, without the scripts. If you are on Premium or Enterprise, use Site optimizer — it is included in what you already pay for, and it does more than this app will.

What it does

1. Shows which containers are closest to a limit, sorted worst-first, so you know where to start rather than reading six numbers.
2. Lists fields nobody filled in, with the count behind each one, and flags migration leftovers first — the fields an import left behind, which are almost always empty.
3. Warns before a dangerous deletion — fields with no attachment but real values, which other tools will happily offer up.
4. Rates deletion safety and explains each rating, in the language of "candidate", never "safe to delete".
5. Points at trash, not delete. Atlassian's own note: trashed fields do not count towards the 700 field limit. You get the headroom back immediately and the decision stays reversible.
6. Exports the shortlist and compares against your previous scan, so cleanup progress is a number rather than a feeling.

It does not delete anything in bulk. That is deliberate: the cost of a wrong bulk delete is higher than the cost of a slower cleanup.

Price

The free tier for small sites is not an introductory offer that disappears later. Small teams get the whole thing.

Prices are the current intention, not a commitment, and will be fixed at release.

Runs inside Jira

Built on Atlassian Forge, so it runs on Atlassian's infrastructure rather than ours. It makes no external calls: nothing about your configuration is sent anywhere, because there is nowhere for it to be sent.

Try the manual version now

Everything the app automates can be done by hand, one field at a time. These are free and need no account:

Find unused custom fields Generates the query for each field, and gives a verdict from the counts Jira returns. Find duplicate custom fields Groups fields that duplicate each other, and explains why same-name fields break JQL. Is it safe to delete this field? Eight checks, including the three cases where an empty-looking field is not empty.