Comparisons → Custom field apps
Jira custom field cleanup and audit apps compared
Jira Cloud now caps a field configuration at 700 fields, and the instances nearest that cap are the old, large, migrated-from-Data-Center ones. This page compares the apps that find what you can safely remove — on price, on rating, and on how destructive their cleanup actually is.
Prices checked on 7 September 2026 · USD list prices, monthly billing, whole site · We publish FastAudit, so read this knowing who wrote it
What each app costs
Monthly total for the whole site, cheapest first after our own row. Note that several of these are field creation apps that also report usage, not cleanup tools — the shortlist below untangles that.
| App | 25 users | 100 users | 500 users | 2,000 users | Rating |
|---|---|---|---|---|---|
| FastAudit — Custom Field Scanner for Jira (ours) | $12.50 | $50 | $105 | $205 | no reviews yet |
| Optimizer for Jira (Health Checks & Cleanup) | $13.25 | $53 | $219.50 | $544.50 | 4.62 |
| Fields - Custom Fields for Jira | $24 | $96 | $297.50 | $692.50 | 4.61 |
| Jira Misc Custom Fields (JMCF) | $25 | $100 | $285.50 | $665.50 | 4.80 |
| Awesome Custom Fields | $26.50 | $106 | $332.50 | $787.50 | 4.95 |
| Doctor Pro: Audit, Optimize & Manage Configuration | $45 | $180 | $495 | $1,145 | 5.00 |
At 25 users FastAudit and Optimizer are within 75 cents of each other. The gap only opens up at scale, and it opens up a long way: at 2,000 users FastAudit is $205 against Optimizer's $544 and Doctor Pro's $1,145, because their curves keep climbing per seat and ours flattens. That is the whole pricing argument, and it is aimed squarely at the sites that actually have a field problem.
Which one to shortlist
- You need to create better fields — calculated fields, scripted values, richer field types: JMCF, Fields or Awesome Custom Fields. These are excellent apps and they are not really in this comparison; they add fields rather than remove them.
- You want a whole-instance health check — fields, plus workflows, schemes, screens, permissions, role actors: Optimizer for Jira or Doctor Pro. Broader than FastAudit by design, and if the field limit is one of five things on your cleanup list, breadth is worth paying for.
- You have a field-limit deadline and want the field question answered properly, with the evidence behind every verdict and a reversible cleanup: FastAudit. One job, done to the end.
Why the 700-field limit changes the maths
The limit is not per project. It is counted against the field configurations your projects use, so three hundred projects sharing one configuration share one budget of 700 — which is why a limit that sounds generous stops being generous the moment your organisation standardised on a handful of shared configurations. Atlassian's own field-configuration screen now shows the count and warns as you approach it, but knowing you are at 640 is not the same as knowing which forty fields nobody has filled in since 2021.
That gap — count versus evidence — is the entire category. FastAudit shows a headroom bar against the limit and, for every field it flags, the evidence it used: how many issues hold a value, when one was last set, which contexts and screens reference it, and whether an automation rule or a saved filter still mentions it.
Evidence, and never deleting
Two rules FastAudit is built around, both worth checking in whatever app you choose:
- Every verdict shows its evidence. A tool that says "unused" without showing you why is asking you to delete production configuration on faith. Ours shows the counts and the references behind each call, so the judgement stays yours.
- Cleanup moves a field to Jira's trash. It never deletes. Jira's own trash keeps a deleted field restorable for a retention window, so an over-eager cleanup is recoverable. FastAudit has no code path that permanently destroys a field.
Also worth knowing before any bulk cleanup, whichever app you use: changes made through an app are attributed in Jira's audit log to whoever authorised them, and a field removed from a configuration is not the same as a field deleted. Read your app's docs on that distinction — ours are on the FastAudit guide.
Why an admin tool should not be priced per seat
FastAudit is opened by one to five administrators, a handful of times a month. Per-user pricing bills that across every licensed user on the site, which means the sites closest to the field limit — old, large, migrated from Data Center — pay the most for a tool three people use. At a textbook $0.40 per user a 5,000-seat site would be asked around $2,000 a month for it.
So FastAudit uses a deliberately sublinear curve: roughly a twenty-four-fold price increase across a four-hundred-fold range of site sizes. The honest cost is that a small paying site pays a little more than a linear price would ask — a linear $0.40 per user is cheaper up to about 150 users, and we are cheaper above it. The pricing page shows that trade in a table rather than hiding it.
What the other apps do better than FastAudit
- They have reviews and we do not. Optimizer's 4.62★ and Doctor Pro's 5.00★ represent real customers reporting real cleanups. FastAudit is new, and the free tier is the only answer we have to that.
- Scope. Optimizer and Doctor Pro audit far more than fields. If your cleanup list includes workflows, screens, schemes and stale role actors, FastAudit will do one item on it.
- Jira's own tooling may be enough. The field configuration screen's Optimize flow and, on Premium and Enterprise, Site Optimizer, both cover part of this at no extra cost. Try them before you buy anything — including ours. Where they fall short is usage evidence per field, which is the reason this category exists.
- We hold no security certification. No SOC 2, no ISO 27001, no independent penetration test — our security page says so in those words.
How these numbers were produced
Every price here was read from
/rest/2/addons/{key}/pricing/cloud/live — the public endpoint the
Marketplace renders its own pricing from — by a script kept in this site's
repository, so no competitor's price list is ever retyped from a screenshot.
Totals assume commercial licences, monthly billing, and that every user on the
site is charged above the free tier, which is how Atlassian bills. Annual
billing is roughly 17% cheaper on every app in the table. See
how Atlassian app billing works for the mechanics.
If a number here is wrong or has moved, tell us and we will correct it — including in our own favour or against it.
Free for sites up to 10 users, permanently
FastAudit is read-only until you ask it to act, and the only action it has is moving a field to Jira's trash.