Cache release issue counters
What does this MR do?
We want to expose milestone issue counts to the API for #31289 (closed).
The current milestones page is also very slow - it has N+1 for the same counters.
We want to cache these counters, but they depend on user, which makes cache useless.
So we want to get rid of user in these calculations and enable cache
I plan to split backend into 3 parts:
- Remove dependency on user to count milestone issue !21554 (merged)
- This MR: Add cache for milestone issue counters - !24284 (merged)
- Expose those counters in the API - !19937 (merged)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Mayra Cabrera