Skip to main content

Cleanup Recommendation

Cleanup Recommendation helps administrators review fields flagged for follow-up after a Custom Fields audit.

Advisory Only​

Cleanup recommendations are advisory and based on Audit 360's analysis. The app does not delete, rename, hide, merge, or change Jira fields.

A recommendation is based on the loaded audit run. If Jira configuration or field usage changes, a new audit run may produce different recommendations.

Decision States​

For each field needing follow-up, record a decision to document your review alongside Audit 360's system recommendation:

  • No decision — the default state before you review a field.
  • Keep — the field should stay as configured.
  • Review later — flag the field for follow-up during a future review cycle.
  • Safe cleanup — the field appears safe to remove or consolidate based on available evidence.
  • Needs migration — the field's data or configuration must be handled separately before any change.
  • Do not change — the field must not be changed, regardless of Audit 360's recommendation.

You can add a short note (up to a few sentences) with each decision to record context or justify your choice. Decisions and notes are stored separately from Audit 360's recommendation, so recording a decision never modifies the underlying audit evidence or metrics.

Run-Scoped Decisions​

Cleanup decisions belong to the specific audit run in which they were recorded. When you run a new Custom Fields audit:

  • Your previous decisions for fields in that older run remain stored but are not visible in the new run.
  • Fields in the new run start with "No decision" as the default state.
  • You will need to review and record decisions again for the same fields if they appear in the new run.

Use this workflow to document your review intent and decisions for governance purposes. Before implementing any changes outside Audit 360, confirm business ownership and external dependencies with relevant stakeholders.