-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
Milestone
Description
Story
We need to increase the current permissions limits that are in place to keep the app fast and reliable, since customers hit the upper limits in production.
Customers hit the limit "Max 100 permissions per group" when granting permissions on the same group to more than hundred fields.
Acceptance Criteria
- ✅ All the new limits are documented here: https://codeclou.io/customfield-editor-for-jira/cloud/admin-guide/get-started/#rate-limits
- 💡 In short:
- ✅ raised the "one group can only be granted to 100 field permissions" up to 2,000.
- ✅ raised the "one user can only be granted to 100 field permissions" up to 2,000.
- ✅ raised the max overall groups the app can handle to 10,000 (groupIndex)
- ✅ raised the groups a user can have up to 100. Meaning: When a user has more than 100 groups, the first 100 will be used to match against the app's permissions. The rest will be cut off. This is due to performance reasons. The app would get very slow to perform 1+ group API requests on every user action and have the 100+ groups checked against existing permissions. Should this rare case occur in production we might increase the limit.
- ✅ the app is still fast on every user interaction
- ✅ we implemented a mechanism that Jira Admins can delete "unknown groups" or "unknown users" from permissions. This is very rarely to happen due to e.g. a group gets deleted permanently and the app still holds permissions for it and cannot retrieve the groupName from the Jira API anymore. Then the group will be displayed as unknown.
Notes
Due to the raising of limits one field context permission could consist of 2,000 groups or 2,000 users.
Therefore we implemented pagination with 15 entries per page on the Permission Editor screen:
