### ~"labels" issues in milestones * [Backlog](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=labels&milestone_title=Backlog&scope=all&state=all&sorted=priority) * [8.15](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=labels&milestone_title=8.15&scope=all&state=all&sorted=priority) * [8.14](https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=labels&milestone_title=8.14&scope=all&state=all&sorted=priority) ### Part of (meta) GitLab discussion product development https://gitlab.com/gitlab-org/gitlab-ce/issues/24688 ### Goals 1. make it easy to share labels across a group 1. make it easy to standardize across the instance 1. new projects should get started easily with new labels 1. projects should remain individual ability to change labels - no change needed Labels added to a project should _never_ override existing labels. If a clash occurs, move on and leave the original labels. ## Proposals - Add the ability to copy labels from another project in the group (even when you already have labels) - solves 1 - Make it possible to adopt global labels, even if you already have labels - solves 2 - When creating a label, provide the option to propagate it to the rest of the projects in the group - (EE) Set standard labels on a group level - solves 3