-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 8.10.0, 8.13.0, 8.13.3, 8.20.2, 8.20.5, 8.20.6, 8.20.10, 8.22.0, 9.4.6
-
Component/s: Project Administration - Users and Roles
-
None
-
8.1
-
18
-
Severity 3 - Minor
-
10
Issue Summary
In Project Settings > Users and roles, filtering by a specific role may not display all users.
Steps to Reproduce
- In a project, have different project roles and include users into each one of them. In the example, we had 628 users at the Developers group, 158 users at the Project Administrator group, and others.
- Access the project role page of the project settings. It will return a list with all users part of a project role in that project.
- Select the option to filter by specific roles and mark the checkbox for the group Developers.
Expected Results
The results should include 628 users, 10 users per page, resulting in 63 possible pages to browse.
Actual Results
The results only go to the 5th page. There is no way to see the rest of the users.
Checking the REST API results for http://JIRAURL/rest/api/2/project/DSP/role/10207 (the Developer list for the DSP project) and everything returned.
However, looking at the behavior in the Network tab for that page load, the actual REST API call is this: http://JIRAURL/rest/projectconfig/latest/roles/DSP?pageNumber=1&pageSize=50&query=
As you click on the pagination, no other network calls occur until you get to page 7. Then this runs: http://JIRAURL/rest/projectconfig/latest/roles/DSP?pageNumber=2&pageSize=50&query=
The problem here seems to be that the Developers list only has enough members to fill 5 pages of the initial list, so he can't get to page 7 to add "page 2" to the results via the second REST API query.
Workaround
Add an additional role to the filter. This will increase the number of pages displayed in the pagination. After the pagination updates, remove the additional role. All pages should show up properly for the original role now.