Allow labels to be restricted to issues-only, or merge-requests-only
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
GitLab has one list of labels, which can be applied to issues or merge requests equally. In several places, when creating a merge request, we now inherit labels from the related issue. Sometimes this happens inappropriately.
Further details
Some labels (like gitlab-ce11710974 or gitlab-ce1567088) relate to human workflows that are issue-only. Inheriting these labels automatically is a nuisance. Even showing them as something to apply to a merge request manually is a nuisance. The same is true for labels like ~"Pick into 11.3", which are merge-request-only - allowing them to be applied to issues is not useful.
Proposal
Allow labels to be marked as "issue-only" or "merge-request-only". Such labels will not be inherited when creating a new MR that references an existing issue, and will not be shown in label dropdowns unless they are being applied to an appropriate object.
What does success look like, and how can we measure that?
When I create a new merge request from a properly labelled issue, the MR will not have gitlab-ce11710974 or gitlab-ce11754980 applied.
Links / references
/cc @smcgivern @victorwu