We have gone through a couple of JIRA upgrades and found that legacy users' user-groups are not modifiable.
It allows the action but does not reflect the removal after the action is completed.
This issue still persists in our JIRA 5.1 test environment with backup data.
Marcus from Atlassian support found that the cwd_membership table had some inconsistencies regarding the groups and directory ids of such groups.
He managed to fix all these memberships by updating the parent_id with the correct group id of the membership directory with a fairly detailed query.
It is currently leveraging Active Directory.
This only happens for users that at one point have been disabled, even after re-enabling they are still left in a stale state.
Adding and removing new groups is allowed, however, removal of older groups (prior to being disabled) are not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the instance using an external user directory such as Crowd, LDAP or Active Directory?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.