-
Bug
-
Resolution: Fixed
-
Medium
-
5.1.2, 5.1.6, 5.2
-
None
-
5.01
-
Background
- User exists in JIRA Internal Directory in lower-case (e.g.: captain.planet).
- User exists in Active Directory Connector in mixed-case (e.g.: Captain.Planet).
- User has membership to group (balsamiq-mockups-editors) in Active Directory only.
- Directory Order is:
- Internal Directory
- Active Directory
Current Behaviour
User membership is calculated in all of the following areas. Screenshots are attached.
- GroupBrowser.jspa is displaying 3, when it should be 2.
- BulkEditUserGroups.jspa is displaying 2 correctly.
- UserBrowser.jspa, is displaying 3, including one that does not have group membership at all. It should only be displayed those two.
Expected Behaviour
GroupBrowser.jspa and UserBrowser.jspa correctly calculate the number of users in the group as 2.
Replication Steps
- Create user captain.planet in the JIRA Internal Directory.
- Add an Active Directory connector.
- Add user Captain.Planet from Active Directory.
- Add a new testgroup group.
- Change Active Director (AD) to be before JIRA Internal Directory (JID)
- Add the Active Directory user to that group.
- Change JID to be before AD.
- View the GroupBrowser, BulkEditUserGroups and UserBrowser to see the incorrect numbers.
We do list duplicate usernames across directories as not being supported in Managing Multiple Directories, however users cannot be easily deleted through the GUI without causing problems.
- is caused by
-
CWD-3143 CrowdService API returns shadowed users depending on the shape of the query parameters
- Closed
- is duplicated by
-
JRASERVER-33014 JQL function membersOf returns incorrect results if the user has groups in another user directory
- Closed
- is related to
-
JRASERVER-33014 JQL function membersOf returns incorrect results if the user has groups in another user directory
- Closed
- mentioned in
-
Wiki Page Loading...