Clear open issues count cache after bulk updating issues state
What does this MR do?
Related to #299178 (closed)
In !49739 (merged) we implemented caching the total count of open issues for a group when the value is over a threshold (currently set at 1000). This cached value expires after 24 hours but would remain unchanged for bulk changes.
In this MR we implement clearing the cached count (both public and total counts) after bulk updating issues state (i.e closing or opening). This is done using a background job to avoid affecting the performance of Issuable::BulkUpdateService.
This implementation clears the cached count for the parent group and its ancestors.
Follow-up to handle MRs bulk updates and issues import: #329543
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
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