Documentation

Overview

Field Hygiene scans every custom field on your Jira site and shows you where it's going wrong: duplicate names, near-duplicates, unused fields, missing descriptions, and how close you are to Atlassian's field-count limits — plus a daily trend of all four counts. It's built entirely on Atlassian Forge, is read-only, and stores almost nothing.

Requirements

• A Jira Cloud site (Field Hygiene does not support Server or Data Center).
• Jira administrator access — the app lives under Jira admin settings.
• Free for sites of 10 users or fewer; a subscription is required above that. See Licensing & billing.

Installation

Field Hygiene is installed by a Jira site administrator from the Atlassian Marketplace:

1. On the Field Hygiene Marketplace listing, click Get it now (or start a free trial).
2. Choose the Jira site to install onto and confirm the requested permissions.
3. Once installed, find Field Hygiene under Jira admin settings → Apps → Manage apps.

The five pages

Field Hygiene is one admin page with five internal routes, reached from the tab bar at the top:

Rescan and Export are always available at the top, regardless of which page you're on.

How detection works

Duplicate names

Field names are compared case-insensitively, with extra whitespace collapsed — "Story Points", "story points", and "Story  Points" all match. A collision is flagged when a warning icon appears if the colliding fields don't even share the same field type, since that's the case most likely to break a report or automation silently.

Near-duplicates

Fields that aren't exact matches are compared by name similarity. A conservative threshold keeps this to genuinely similar names — shown with a similarity percentage so it reads as a suggestion, not a confirmed duplicate.

Unused fields

A field is flagged unused when it isn't attached to any screen, or when Jira has tracked no activity on it for two years or more — the same bar Atlassian's own Site Optimizer uses, made available here without needing a Premium or Enterprise plan.

Field-count limits

Company-managed (classic) projects share a 700-field budget per field configuration scheme; team-managed (next-gen) projects have a separate 50-custom-field cap per project. Field Hygiene tracks both, since they're genuinely different limit models.

Data & permissions

• Two scopes. read:jira-work and manage:jira-configuration, and every interactive scan acts as the admin viewing the page — it can never surface anything they couldn't already see.
• Almost no storage. Only a daily aggregate count for Trends (four numbers). Everything else is computed fresh on every page load.
• No third parties. Everything runs on Atlassian Forge. No data leaves the platform.
• Never writes. Field Hygiene never renames, merges, or deletes a field — it reports, you act in Jira.

Full detail is in the privacy policy.

Licensing & billing

Free for Jira sites of 10 users or fewer. Above that, Field Hygiene is licensed and billed through Atlassian on a per-seat basis — the same features ship at every tier, with no functionality held back on the free plan.

Licensing is managed by your Jira site administrator from Manage apps in Jira administration.

Troubleshooting

The scan says "Could not read field data from Jira."

This usually means a temporary connection issue reaching Jira. Click Rescan; if it persists, contact support.

The field-limit section shows a warning instead of numbers.

Field Hygiene soft-fails the field-limit check independently of the rest of the scan — duplicates, unused fields, and missing descriptions are still accurate even if this one section couldn't complete. Try Rescan.

Trends says "Building history."

Trends takes one snapshot a day, automatically. You'll see a real chart once at least two days have passed since install — there's no way to speed this up.

I found a duplicate but I'm not sure which one to keep.

Field Hygiene deliberately doesn't guess which field is "correct" — creation order isn't a reliable signal for which one is actually in use by reports or automations. Check usage in Jira directly before deciding.

Version history

Support

Questions, problems, or feedback? Email support@isogunlabs.com. Best-effort support; typical response time is 1–2 business days.