Remove `unfiltered_epic_aggregates` feature flag
What does this MR do?
Remove the unfiltered_epic_aggregates
feature flag in the backend and frontend.
@johnhope set the feature flag to on
on 14 March.
@cngo defaulted the feature flag to default to "on" with !26919 (merged), and it has been on gprd
with no issues for about 6 days.
Because we are removing code from fields that use the DescendantCountService
, we can also reduce the complexity of these fields.
Related to #208857 (closed)
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 🤖 GitLab Bot 🤖