Labels are a widely used primitive in GitLab. There are several things we need to do to improve their quality of life: - [Double confirmation](https://gitlab.com/gitlab-org/gitlab/-/issues/23772) when attempting to delete a label. This is a very destructive action *OR* [archive labels](https://gitlab.com/gitlab-org/gitlab/-/issues/4233) instead of deleting them. - Set priority on [Group labels](https://gitlab.com/gitlab-org/gitlab/-/issues/213644). The priority cascades down to Projects. Projects can add/remove Project labels to the "Prioritized Labels", can change the relative order between Project and Group labels but cannot remove prioritized Group labels. [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/16920) - Properly show inherited labels in all sub-groups and projects. [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/18034), [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/25908) - Easily show the origin of labels. [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/199313) - Make labels be promotable up an entire tree [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/208410) and prevent duplicate labels from being created in a group/sub-group/project tree. [ref](https://gitlab.com/gitlab-org/gitlab/-/issues/24553) - Allow glob filtering of scoped labels in the filter bar. - Prevent duplicate label creation when moving issues between projects and provide a warning model of potential data loss when moving an issue into a project that doesn't have the same labels. - Improve the UX of the label list as a whole -> consider grouping scoped label sets together, etc.