One scan of your site. For every custom field: how many work items actually hold a value, and which saved filters and boards would break if you deleted it.
Built and running · Atlassian Marketplace listing on its way
The app works on a live Jira Cloud site today. This page will link to the Marketplace listing once it is public. Until then, questions to hello@configscope.com. The free tools already work, one field at a time.
Every cleanup tool for Jira decides whether a custom field is "unused" by one of two signals: whether it is attached to a screen, or whether anyone ever filled it in. Both tell you whether a field is empty. Neither tells you whether something depends on it.
A saved filter that says "Story Points" > 3. A board that estimates in Story Points. A quick filter on cf[10031]. Delete the field and every one of those breaks, whether or not the field held a single value. The admin who deletes it finds out from the people whose board stopped working.
Configscope lists those dependencies, per field, next to the value count. Then the verdict is simple: a field with no values and nothing depending on it can go; a field with no values that a board still names is a trap, and it is listed first.
cf[id]), every board that uses it as the estimation field, every board quick filter that mentions it, and every board built on a filter that does. Shown as a short list at the top, sorted by how much would break.| Verdict | What it means |
|---|---|
| Would break | No values, but a filter or board still names it — or it carries a default value that makes it look empty. Deleting it breaks something. Listed first. |
| Unused | No values, no default, nothing found that depends on it. |
| Likely unused | No values and no dependencies found, but the default-value check was unavailable for this field. |
| Check by hand | Jira gives this field type no search, so no app can count its values. Look in the field's own configuration. |
| In use | Work items hold values. Not a deletion candidate; its dependencies are still listed. |
| Locked | Jira does not allow deleting it. |
Nothing is deleted, trashed or edited. Removal stays in Jira's own admin screens, done by you.
On our own long-lived Jira Cloud site, with 262 custom fields, a scan takes about a minute and comes back with 44 fields that can be removed now, 18 that probably can, 179 in use, and 21 that Jira cannot count for any app.
The part that matters is the dependency list above the table. Rank is named by 21 saved filters. Story Points is the estimation field on four boards — and appears on no screen at all, so an attachment-based tool would have offered it for deletion.
Jira does not expose everything to apps, and the scan says so on screen rather than staying quiet:
So the verdicts are advisory. A field with no values and no dependencies found can still be used by an automation rule. Treat the result as a shortlist to review, not a delete list.
Atlassian's configuration limits apply on every plan. The tooling does not: Site optimizer is available on Premium and Enterprise only. Atlassian's own documentation tells Standard administrators what to do instead:
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 audit, without the scripts. If you are on Premium or Enterprise, Site optimizer is included in what you already pay for; this app adds the dependency question it does not ask.
Built on Atlassian Forge and running on Atlassian's infrastructure. It makes no external calls and keeps no storage of its own: the scan result lives on your screen while the page is open, and nowhere else. Only site administrators can open it. The permissions it asks for are read-only and each one maps to a specific thing the scan reads — listed here.
| Site size | Price |
|---|---|
| Up to 10 users | Free, permanently |
| Above that | Per user per month, via the Atlassian Marketplace |
The free tier for small sites is not an introductory offer that disappears later. Small teams get the whole thing. The per-user price is set when the listing goes live, and will be on the listing.
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. Is it safe to delete this field? Eight checks, including the three cases where an empty-looking field is not empty. Find duplicate custom fields Groups fields that duplicate each other, and explains why same-name fields break JQL.