Remove confidential_epics_query feature flag
What does this MR do?
Enables filtering of confidential epics in EpicsFinder. This has been enabled globally on gitlab.com for last month and it doesn't have visible negative performance impact on epic queries (#213075 (comment 346583832)).
No changelog is included because this is only backstage/internal change, because confidential epics are not enabled by default yet. This extra "backend/internal" flag was present to assure that confidentiality query works well so we don't have to turn it off later in case we would have to turn off confidential_epics which would cause that previously confidential epics would be listed too (#213075 (comment 347283596)).
Closes #213075 (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