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 🤔