How do you handle Jira asset cleanup when an employee leaves?

[Abenezer Anglo]

Hey everyone,

Curious how other admins are handling this. When someone leaves the company, what's your process for cleaning up their Jira footprint?

Specifically things like:

Filters they owned that others depend on

Dashboards they created

Open issues still assigned to them

Component leads, automation rules, etc.

We've been doing it manually and it's honestly a nightmare, especially when the person left suddenly and nobody knows what they owned.

Do you have a process that works? A script? Do you just leave the orphaned assets and deal with it case by case?

Would love to hear how others are tackling this. Feels like something that should be easier than it is.

[Tomislav Tobijas]

Ah... ,@Abenezer Anglo from my experience, it's mainly being done manually after a specific number of months (or even years 🫠)

I believe one of our clients did mention the idea of using the scripts for this, but I'm not sure if they've moved forward with that solution.

You actually gave me an idea, as part of offboarding, to actually add tasks related to entity review and cleanup. 
The main problem is that some of the entities are shared with other users; so, you'd need to find a new owner for such entities (e.g., dashboards, filters, etc.)

I'm not even sure if there are Marketplace apps that actually work on this principle, and which would recommend what's ready for cleanup. Atlassian could also think about adding those additional insights as part of site optimizer to make Jira admins' lives easier... potentially 🤔

[Abenezer Anglo]

Thanks @Tomislav Tobijas , really helpful. I'm actually exploring building a tool for exactly this. Would you or your clients find value in a one-click solution that scans a departing user's assets and bulk transfers them to a new owner?

[Matthew Joslin_AppFox_]

There's no single native "hand over everything" action, unfortunately. Jira spreads ownership across several places, so the most reliable approach is to reassign in passes before you deactivate the account (deactivating first orphans shared filters and dashboards, which is the usual headache):

• Shared filters & dashboards: admins can reassign owners under Settings → System → Shared filters / Shared dashboards.
• Open issues: bulk-edit via JQL (assignee = "leaver") to reassign in one go.
• Component leads & project leads: updated per project under project settings.
• Automation: check the rule actor/owner under Project and Global automation and reassign.

Keep the account active until those are moved, then deactivate.

If you're handling turnover regularly, the per-project clicking really doesn't scale. Optimizer for Jira does bulk actions across the instance - including reassigning project lead/ownership across many projects at once - which is built for exactly this inherited-items problem. It also surfaces orphaned and unused config, so you can tidy up while you're in there rather than leaving it for the next person.

It also has lots of audit features and a Rovo assistant to help you get a clear view of what you're looking at before you make any of the more dramatic amends!

[Abenezer Anglo]

Thanks @Matthew Joslin_AppFox_  really helpful context. Optimizer looks great for the broader admin toolkit use case. I'm actually exploring building something more focused specifically on the offboarding handover flow, the one-click 'transfer everything this person owned to someone else' action. Is that a workflow your users specifically ask for, or does Optimizer already handle that end to end?