I am comming across this every now and than and it is a real PITA (imho)! If a user is deleted in JIRA (or no longer synced from the LDAP) working with jira is a mess. This can occure e.g. if someone leaves a company...
The following scenarios with removed users make me facpalm a lot:
Fur us we often have to remove users for different reasons and this usually done by removing them from the LDAP. How should we approach above stated problems? Or how would a process look like in order to avoid said problems?
Thanks and Cheers, David
from my experience it is a PITA (never used that acronym before but I like it!), maybe even a RRPITA (a Right, Royal PITA)
First, I presume you've read these:
Editing issue after user deleted
How do we handle it? We periodically sweep the user database and have a script which checks if they are still in the LDAP server. if not, we remove all groups and add them to a marker group (Dead Accounts) and deactivate them. We also get reports from HR about leavers and the suport team does manual updates to reassign issues which are assigned to the dead account. becomes a bit more complex when they are project lead as well, you have to manually look for that.
The whole way user accounts is handled is a bit of mess but it's getting better in Jira 5.
Yes, I know both ressources. The thing is, deactivating a user is not available when the user has just been excluded from the LDAP sync. So the process would be:
Now one would be save, korrekt?
If a user is deleted from the LDAP engine (typically Active Directory), when JIRA periodically synchronises (if using a connector) that user will be deleted in JIRA. As linked earlier, we recommend to deactivate users rather than deleting them as it can cause a number of problems in JIRA. You could workaround this with any of the following (this is also summarising from some earlier answers):
I am having this situation appear, as well. I am in a very large company (60K+ possible users in LDAP) and have no control/influence over the process for removing employees from LDAP.
So #1 won't work.
I use the LDAP diretory to manage my groups because those groups are used in other systems, as well (not just JIRA).
So #2 won't work.
Lastly, I don't know when a user is deleted unless I stumble upon one of his/her tickets and see the grayed user name. So since I don't know when users are deleted from LDAP, I can't do #3.
So #3 won't work.
Is their a #4? At a mininum, I'd like a filter (JQL statement) that flags these orphaned users to my attention. Then maybe I could manually do #3 or otherwise reassign.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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