Skip to main content

Custom Fields Limitations

Custom Fields audits depend on the Jira APIs, permissions, and metadata available to the app at audit time.

Current Limitations​

  • Results are advisory and may not prove runtime impact.
  • Jira API coverage can be partial when permissions or endpoint behavior limit visibility.
  • Field display-name matching can produce false positives.
  • Smart value, JQL, and workflow detection are best-effort.
  • Count-only population checks do not store work item keys or issue details.
  • A field with no detected usage is not guaranteed safe to delete.
  • Locked custom fields and fields without usable lock-state metadata are outside the Custom Fields audit scope.

Review important fields with business owners and Jira administrators before making configuration changes.