...
When a space group is selected, the app begins to load the group membership data for that group. When this group is excessively large (high thousands, or tens of thousands of members), this can take significant time to load.
Solution
There is no solution available currently. While we have solutions for the problem developed, there are some roadblocks with Confluence's API which prevent us from delivering a solution. Please consider either directly up-voting/commenting on the below issues, or refer to these issue keys in support correspondence with Atlassian:
- https://jira.atlassian.com/browse/CWD-4479
- https://jira.atlassian.com/browse/CWD-3512 (marked as fixed but not working in current Confluence versions)
We are in contact with Atlassian, asking them to address these issues as soon as possible. Please let us know if you are having big problems with thisWe are working on the following issues regarding Group/Group membership retrieval and performance:
https://thepluginpeople.atlassian.net/browse/CSUM-77 https://thepluginpeople.atlassian.net/browse/CSUM-296 https://thepluginpeople.atlassian.net/browse/CSUM-301 (not visible to public)
This issue has been resolved in CSUM v. 3.1.3, by enabling the serverSide pagination settings from the Admin page, which implements proper paging to load only the Groups/Group Members of the selected page.
Related articles
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
| Page Properties | ||
|---|---|---|
| ||
|