`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.
- #12631 (closed) Environments Dashboard: Explore front-end implementation (mvc) and suggest UX improvements Deliverable, ~"Release", UX, UX debt, ~"devops::release", frontend, ~"group::progressive delivery", usability
- #12562 (closed) Merge trains can fail due to pipeline running in a refreshed merge ref ~"P1", ~"Release", ~"S1", ~"devops::release", ~"group::progressive delivery"
- #12423 (closed) Better exclusive lock for merge trains ~"P2", ~"Release", ~"S2", ~"bug", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery"
- #12267 (closed) Merge When Pipeline Succeeds (MWPS) cannot be chosen while Merge Trains option is enabled ~"Accepting merge requests", ~"Release", UX, ~"devops::release", ~"devops::release::merge trains", feature, frontend, ~"group::progressive delivery"
- #12149 (closed) Environments > Deploy boards > Improve UI ~"Release", UX, UX debt, ~"devops::release", frontend, ~"group::progressive delivery"
- #12133 (closed) Cancel message for "Add To Merge Train When Pipeline Succeeds" auto merge strategy is not descriptive enough ~"Release", UX, ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery", ~"technical debt"
-
#12131 (closed) Optimize merge train related queries with
target_project_idandtarget_branch~"Release", ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery", ~"technical debt" - #12027 (closed) Improve color accessibility of Canary Deployments pods ~"Accepting merge requests", ~"Release", UX, accessibility, ~"devops::release", ~"group::progressive delivery"
- #11649 (closed) (confidential) ~"(confidential)"