I was surprised to findout that Jira users do not appear to be disabled when their accounts are disabled on LDAP.
Yes, they are not able to login anymore into Jira but still the other users do not see them as disabled users while browsing.
In fact it is even impossible to deactivate them if you are using LDAP, the option being available only when you user local directory.
The old way of "disabling" users was to remove all group memberships for the users but this is a very bad practice, as people may leave the company and return after, and sometimes this can even happen if they switch between temporary or permanent employee.
AD/LDAP has a good practice of maintaining the same account for everyone, for ever, only disabling them when people leave.
How can we solve this problem and be able to see the people left the company (diabled LDAP accounts) as disabled account in Jira.
This is essential because it allows people to reasign bugs to others when they see the "crossed" line above the disabled users.
This is a known improvement request:
LDAP Delegate: Synchronize with AD to disable deleted users > https://jira.atlassian.com/browse/CWD-2478
I encourage you to vote on the ticket above and add yourself as a watcher. In case of updates, you'll be notified by email.
However, perhaps you may try to create a custom BATCH script or any other customization for auto-update the JIRA memberships after monitoring LDAP actions. Don't forget to use the developers.atlassian.com as a reference regarding the JIRA structure.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs