`devops::release` issues without a category label

Attention @ogolowinski and @cstasik, 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.

  • #12870 (closed) Environments dashboard: Indicate to users that removing/adding a project from one dashboard view, affects all others ~"Release", UX, ~"devops::release", ~"group::progressive delivery"
  • #12869 (closed) Environments dashboard: Improve the Add project modal ~"Release", UX, UX research, ~"devops::release", ~"group::progressive delivery"
  • #12799 (closed) Show helper text about merge trains under "Validate the post-merge result would pass prior to merging" option ~"Release", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery"
  • #12796 (closed) Remove merge_trains_enabled column from project_ci_cd_settings table ~"Accepting merge requests", ~"Release", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery", ~"technical debt"
  • #12795 (closed) When pipelines for merged results failed, it shows ref path instead of branch name ~"P3", ~"Release", ~"S3", ~"bug", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery"
  • #12631 (closed) Environments Dashboard: Explore front-end implementation (mvc) and suggest UX improvements Deliverable, ~"Release", UX, UX debt, ~"devops::release", ~"devops::release::discovery", environments, frontend, ~"group::progressive delivery", usability
  • #12149 (closed) Environments > Deploy boards > Improve UI ~"Release", UX, UX debt, ~"devops::release", environments, frontend, ~"group::progressive delivery"
  • #11649 (closed) (confidential) ~"(confidential)"