Free for up to 10 users, 30-day free trial for larger sites. Runs entirely on Atlassian. For Jira Cloud administrators.
In four lines
The problemCustom fields pile up in Jira. Nobody knows which ones are still used, so nobody deletes them.
Where it is on screenJira settings, then Field Sweep under Apps. The Overview tab shows the breakdown. The Fields tab lists every field. Jira administrators only.
What you doPress Scan. Field Sweep reads your saved filters, boards and dashboards and sorts every custom field into Can clean up, To review or nothing found.
What you getA short list of fields to check before you delete, with the places each one is used, and a plain statement of what the scan could not read. The CSV export keeps a record.
What you can do
See which custom fields nothing uses
One scan sorts every custom field into three groups. A field counts as Can clean up only when the scan found no filter, board or dashboard reference, it is on no screen, no other field shares its name, and Jira shows no recent value change.
Every finding comes with next steps
Open a finding to see the fields with their IDs and the steps to take in Jira: check automation and workflows first, then delete. Field Sweep itself changes nothing.
It tells you what it could not read
The scan lists the places it never reads (automation rules, workflow conditions and post-functions, dashboards not shared with you, swimlanes and card layout), and the items it tried but could not read. A gap is never shown as zero.
See what uses a field
The Fields tab shows each field’s screens, contexts, last-used date and references. References opens the list of saved filters, boards, quick filters and dashboards that use it. Fields that share a name are marked so you can tell them apart.
Your rules, and a CSV
Set how many days without a value change counts as unused, and exclude field IDs from the delete candidates. Export the result as a CSV.
What it does not do
It never deletes or changes anything. You delete a field yourself in Jira, after checking automation and workflows.
It does not read automation rules, workflow conditions, validators and post-functions, dashboards that are not shared with the scanning administrator, or swimlanes and card layout. The Overview lists these, so you can check them by hand.
Only Jira administrators can open it. The scan runs with the permissions of the administrator who starts it.
The Fields list, Settings and the CSV need a license. A scan and the Overview counts work without one.
Questions
What does “Can clean up” mean? Is anything actually deleted?
Field Sweep never deletes or changes anything. “Can clean up” is a starting point for your own review: a field with zero references in the areas Field Sweep can read, on no screen, with no shared name, and no recent value change. Fields that share a name, or results from a scan that could not check everything, are listed under “To review” instead of being guessed at.
Why does the Overview say what the scan did not read?
Because Field Sweep would rather say what it did not read than quietly show zero. Some places cannot be read by any app (for example, automation rules and unshared dashboards). The Overview lists them, so you know what to check by hand.
How long does a scan take?
Large sites are processed in resumable chunks in the background. You can close the tab, come back later and press Reload.
Does my data leave Atlassian?
No. The app runs on Atlassian. Details are in the privacy policy.
What does it cost?
Free for up to 10 users. Larger sites get a 30-day free trial, and current pricing is on the Marketplace listing.