Duplicate named Labels and Milestones across Groups and Projects are difficult to distinguish when assigning to an Issue
Problem to solve
As a User of labels,
I'd like to be able to differentiate between duplicate label names when they exists at the project vs group level,
So I can assign the right label to issues and epics
Intended users
- Rachel (Release Manager)
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Presley (Product Designer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Dana (Data Analyst)
Further details
@gweaver and I came across this while recording a product demo.
You can create a duplicate named label at the Group level, if it already exists at a Project level, however, you can not create a duplicate label at the Project level if it exists at the Group level (due to label inheritance).
When attempting to create a duplicate label at the project level you receive an error:
If I create a label at the project level first Waiting
and than create a label with the same name Waiting
at the group level I end up with a listing like this:
Above, you can differentiate via color (not ideal) and description only, but if I attempt to assign a label to a Project level issue I get:
While I still have differentiation via color, there is nothing else that communicates which label is which.
Similarly the same happens with Milestones:
Proposal
We should identify a simple way to communicate if a duplicate label/milestone exists at Project or Group level.