Skip to main content

Custom Fields Limitations

Custom Fields audits are advisory and depend on available Jira APIs, permissions, and metadata at the time of the scan.

Analysis Limitations​

  • Results are heuristic and do not prove whether changing or removing a field would impact Jira at runtime.
  • Field display-name matching (for detecting duplicates) can produce false positives when similar names appear by coincidence.
  • Detection of smart values, JQL patterns, and workflow field references are best-effort and depend on Jira API metadata availability.
  • Locked custom fields and fields where Jira does not report lock state are excluded from the audit and not analyzed.
  • A field with no detected usage across screens, configurations, filters, boards, workflows, and population checks is not guaranteed safe to delete without further review.
  • Count-only population checks report whether a field has data in work items, not how many work items or what values they contain. Work item keys and issue details are not stored.

Coverage Limitations​

  • Audit 360 relies on public Jira REST APIs. Workflow and board visibility depend on what Jira endpoints expose; uncovered areas are reported as coverage notes.
  • Jira API coverage can be partial when permissions or endpoint behavior limit visibility to certain configuration elements.
  • Latest audit auto-load is based on completed, non-deleted runs stored in the app's database. If that storage fails or becomes unreadable, Audit Overview shows an error state instead of mixing data from another source.

Execution Limitations​

  • Only one Custom Fields audit can run at a time on a Jira instance. If you start a new audit while one is already running, you are returned to the in-progress audit instead of starting a second one.
  • If a running audit stops reporting progress for an extended period (typically several minutes), Audit 360 automatically marks it as failed to prevent it from appearing to run indefinitely.
  • A run shown as your "latest" result is always the newest non-deleted, completed audit run. Runs that are still in progress, queued, or failed are never shown as the latest result.

Before implementing any changes based on audit results, review important fields with business owners and Jira administrators outside Audit 360.