Enable work_item_features_field by default
What does this MR do and why?
All three widget-splitting MRs are merged and live in production, so the work_item_features_field flag can move from wip to beta and default on for every instance. wip flags can't be default-enabled, hence the type change.
This also drops the suite-wide stub_feature_flags(work_item_features_field: false) from spec_helper.rb, so RSpec exercises the features path rather than the widgets one.
Draft on purpose: holding this for a week so any breakage from the merged splits can surface in production first.
References
- #587972 (closed)
- gitlab-org#20609
- Blocked by !253547 (merged), which adds the missing unauthenticated complexity guard for the work item detail queries.
- Blocked by !259817 (merged), which fixes the
featurespath bugs this MR's pipeline surfaced on boards and epic linked items.
How to set up and validate locally
-
Make sure the flag is unset locally, so the new default applies:
Feature.remove(:work_item_features_field) -
Open a work item and confirm it renders, then check the network tab shows
namespaceWorkItemrequestingfeaturesrather thanwidgets. -
Sign out and open a public work item, and confirm it renders instead of
Work Item not found.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.