Jira Cloud · Custom field cleanup
Firebreak for Jira
Trail report · Firebreak
Cut the break
Find the custom fields nobody uses, see what still depends on them, and clear them before they slow Jira down.
| Field | Last change | Deps | Status |
|---|---|---|---|
| Story Points (Legacy) | 14 mo ago | 32 | Blocked |
| Team (old) | 22 mo ago | 6 | Review |
| Approval Date | 26 mo ago | 0 | ✓ Safe |
| Team [Legacy] | never | 0 | ✓ Safe |
Preview · Firebreak
Know before you delete
Firebreak isn't on the Atlassian Marketplace yet. These screens show the app with demo data, and the released version may differ.
01 · Survey Find the fields nobody uses
One scan covers fields, filters, boards, screens, workflows and contexts. Fields untouched for a year, with no dependencies and not locked, go in a safe-to-trash queue.
02 · Import Add your automation rules
Jira's API doesn't show automation rules to apps, so you import the rules export once. It's read in your browser, and Firebreak keeps only which fields each rule uses.
03 · Impact See what depends on a field
Every rule, board, workflow, filter and screen that uses a field, and the boards and dashboards behind those filters. Each link shows its severity and the evidence for it.
04 · Simulate Know what breaks first
A read-only report of everything a deletion would break, by severity, with an owner and a suggested fix for each. Fields with critical dependencies can't go to trash until they're fixed.