`devops::release` issues without a category label

Attention @ogolowinski, The following issues have been identified in the devops::release stage that do not have a category label. These should be applied with urgency so that important issues are not being lost track of.

  • #14046 Allow users to define any strategies in GitLab Feature Flag system ~"devops::release", ~"devops::release::feature flags", feature, ~"group::progressive delivery"
  • #14017 (closed) GitLab Feature Flag: userWithId strategy is persisted with default strategy. ~"P2", ~"S2", ~"bug", ~"devops::release", ~"group::progressive delivery", needs investigation
  • #13993 (closed) Public API support for Merge Train api, ~"devops::release", ~"devops::release::merge trains", feature, ~"group::progressive delivery"
  • #13991 (closed) Drop detached_merge_request_pipeline and merge_request_pipeline keys from MR widget API ~"Accepting merge requests", ~"devops::release", ~"technical debt"
  • #13832 (closed) Merge Request enviroment url not showing up on first deploy ~"GitLab Enterprise Edition", ~"devops::release"
  • #3277 Director Level Management Dashboard ~"Accepting merge requests", Create [DEPRECATED], ~"GitLab Enterprise Edition", GitLab Ultimate, Manage [DEPRECATED], ~"Release [DEPRECATED]", UX, ~"devops::release", feature, ~"group::release management", maturitycomplete, ~"release::validation::backlog"