Optimize performance of release evidence with pagination of the issue summary in JSON
Problem to solve
When reviewing #34402 (closed), we identified there was no pagination on the issue summary, so large amounts of data can be returned, placing a performance strain on the system.
Intended users
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
Further details
- There may be other ways to optimize the issue summary, this issue will do so by adding pagination
- Please add additional suggestion to the description/comments for review
Proposal
- Add pagination to the issue summary so that results are limited
Permissions and Security
- Permissions should inherit that of the data to prevent unauthorized users having access to data they would not be able to access in GitLab UI or API.
Documentation
Testing
- Access to the data in the issue summary should follow the proper data permissions (for example, if a user is not logged in/authenticated then they should only get paginated results for a public access user)
What does success look like, and how can we measure that?
- Users should have no performance impacts when using release evidence & release summaries in GitLab
What is the type of buyer?
- Community
- Premium +
Links / references
Edited by Rayana Verissimo