Jira and Confluence Governance

Overview

I lead Jira and Confluence governance across multiple departments: designing custom fields and screen schemes, building lifecycle automation for content archiving, and cleaning up what accumulated before that structure existed.

Problem

Atlassian tools degrade by accretion. Every team that needs “just one more field” gets one, every project spawns its own scheme, and every page written for a project that ended three years ago stays in search results forever. No single step is a mistake. The cumulative result is issue creation forms full of irrelevant fields and Confluence search returning confidently wrong answers from abandoned pages.

The administrative cost compounds too. More schemes means more objects to maintain, and every small change requires checking what else it touches.

Approach

I treated it as a schema problem and a lifecycle problem, separately.

Schema consolidation. Rebuilt custom fields and screen schemes so departments share structure where their needs are the same and diverge only where the work differs. Fewer objects to maintain, and issue forms that ask for what a team needs instead of the union of what every team has ever needed.

Content lifecycle automation. Built automation that archives stale content on defined rules, so aging out is the default state and not a cleanup project someone has to volunteer for. This is what stops the problem re-accumulating.

Backlog cleanup. Worked through the existing accumulation as well as fixing the forward path. Automation applied to a system already full of stale content only preserves the mess more efficiently.

Architecture

Shared field and screen schemes across departments with documented divergence points, plus rule-based archival automation that acts on content age and activity without manual review. Governance decisions are written down, so the next administrator inherits the reasoning and not a set of unexplained configuration objects.

Outcome

Administrative workload down 35%, with better platform scalability: fewer schemes to maintain, cleaner issue creation, and search results that surface current documentation instead of abandoned pages.

Lessons Learned

Cleaning up an Atlassian instance without changing what let it get messy only resets a clock. The archival automation mattered more than the cleanup. One is a project with an end date; the other is the reason there is no second cleanup project in two years.