What actually stops Jira seat cleanup from being fully automatic in your environment?
For a lot of teams, it is not the idea. It is the exceptions: unmanaged accounts, service-account-like users, inherited access paths, and approval requirements that make teams hesitate.
I am building in that exact cleanup-review lane here:
https://unitlane.net/products/license-guard/
Curious which blocker is the real one in practice.
