Run a Jira custom-field audit loop that reduces clutter without breaking reports or automation.
The instance has too many custom fields, but some fields still power reporting and automation. PDCA reduces cleanup risk by testing changes before permanent deletion. Do not delete a field just because issue count is low or the name looks duplicated. Field list is cluttered, duplicates confuse users, and prior deletion broke dashboards. Each cleanup candidate has owner, dependency evidence, reversible test, measured result, and documented decision. Plan the candidate set Select duplicate or ownerless fields; collect context, issue count, JQL, dashboards, automation, and app references Planning defines what evidence must be true before cleanup. Do a reversible test Hide…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in