Field Limit Guard — Documentation

Field Limit Guard is a read-only Jira Cloud admin app that scans your custom fields, flags cleanup candidates, and shows where each field is used — so you can stay under Jira’s configuration limits and clean up safely. It never deletes anything.

Getting started

1. Install Field Limit Guard from the Atlassian Marketplace.
2. In Jira, open the settings gear, then go to Apps and select Field Limit Guard. (It is an admin page, so you need Jira administrator access.)
3. The app scans automatically on open. Use Rescan to refresh.

Reading the dashboard

The Overview tab summarises your custom fields by risk:

• High — a deletable field that is on no screen and has a corroborating signal (never used, stale, or a duplicate name). The strongest cleanup candidates.
• Medium — a deletable field with one signal worth reviewing (for example, not on any screen).
• Low — in active use; no cleanup signals.
• Managed — owned by Jira or an installed app and not deletable. Shown for awareness (it still counts toward field limits) but kept out of cleanup candidates.
• Unknown — the app could not read enough signal to score the field.

Risk is advisory. Always review a field’s detected dependencies before deleting it.

Field detail

From the Inventory tab, select Details on any field to see its detected dependencies: screens, contexts, options, project associations, and the saved filters that reference it. You can dismiss a warning to hide a field you have reviewed and want to keep.

What the app does not check

By design, Field Limit Guard does not inspect automation rules or workflow conditions and validators. Atlassian does not expose automation rule contents to apps, and workflow rule parsing is not included in this version. Review those manually before deleting a field. The app surfaces this limitation in the field detail view.

Reports

The Report tab generates a full cleanup report you can copy as CSV or Markdown for review, sign-off, and change tracking.

Permissions and data

The app reads field configuration metadata only and stores nothing beyond your dismissed-warning preferences. It reads no issue content and stores no personal data. See the privacy policy for the full detail and the exact scopes used.

Support

Questions or issues: support, or email hello@ariacode.dev.