Find which Jira custom fields your saved filters, boards and dashboards use, and which fields nothing uses. A scan only reads. After a review, a Jira admin can move unused fields to Jira’s trash and restore them later. Field Sweep never deletes a field for good.
Try it on the Atlassian Marketplace Getting started: your first scan in four steps 日本語のページ
Free for up to 10 users; see the Marketplace listing for paid tiers. Runs entirely on Atlassian. For Jira Cloud administrators.
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.
Open a finding to see the fields with their IDs and the steps to take in Jira: check automation and workflows first. For fields nothing uses, you can then move them to Jira’s trash from the same row.
On the Overview, open Fields nothing uses and press Choose fields to move (up to 25 at a time), or use Move to trash… on a row of the Fields tab. Before anything moves, Field Sweep checks each field with Jira again and shows a review: the screens it leaves, about how many work items hold a value, and the places the scan could not read. You tick the boxes it asks for (for some fields you also type the name or ID), then press Move N to trash. Jira calls this Delete. It needs a license and a scan from the last 24 hours.
The Moved to trash tab lists each field the app moved: when, by whom, its state now, and the day Jira deletes it for good. Press Restore to bring a field back. According to Atlassian, its values, screens and contexts come back. Jira deletes a trashed field and its values for good after 60 days.
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.
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.
Set how many days without a value change counts as unused, and exclude field IDs from the delete candidates (after the next scan, an excluded field cannot be moved to trash). Export the result as a CSV.
Not by a scan: a scan only reads. If you choose to, you can move a field to Jira’s trash from the app, after a review, and restore it from Moved to trash. Jira deletes a trashed field for good after 60 days; Field Sweep never does. “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.
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.
Large sites are processed in resumable chunks in the background. You can close the tab, come back later and press Reload.
No. The app runs on Atlassian. Details are in the privacy policy.
Free for up to 10 users; see the Marketplace listing for paid tiers.
Try it on the Atlassian Marketplace
Questions? Support or support@hullspark.com.
Hullspark