Hi everyone,
A few days ago, I ran into a situation that seemed pretty straightforward:
👉 Deactivate a user who left the company.
But here’s what happened next 👇
❌ An approval workflow stopped working
❌ Automation rules silently failed
❌ A dashboard started showing incomplete data
❌ Some users suddenly lost access to a project
No errors. No warnings… just things quietly breaking.
Because in Jira, users are deeply embedded across many configurations:
👉 The tricky part is that these dependencies are not always visible before making a change.
These two actions are often confused:
🔴 Deactivate a user
🟠 Remove from groups
Before making any change:
✔️ Check workflow dependencies
✔️ Review automation rules
✔️ Transfer ownership of filters and dashboards
✔️ Audit groups and project roles
✔️ Reassign critical issues
In larger Jira instances, doing all of this manually can quickly become time-consuming and error-prone.
To make this easier, I started working on a small app that helps analyze the impact before deactivating a user — for example:
I initially built it to solve this exact problem internally, but I thought it might be useful for others facing the same challenges:
How do you handle this today?
mir_contact_stable_point_io
0 comments