Label confusion around organization structure.
Issue
As a user, I want to tag a known label to my issue. However, label behavior is not uniform or standardized, and feels like I must create new labels "arbitrarily."
| 
|
I know there's a UX label in my organization, and yet it does not appear here.
- Labels do not exist globally, despite being tied to one organization.
- Labels appear to be tied to groups.
- Creating redundant labels because they do not exist globally, causes confusion. Why am I missing a known label? When I search globally, why do I have multiple redundant labels.
Suggestion
- Reconfigure the label behavior to be global, rather than group based.
- Labels are an organizational concept tied to a root level architecture. Example: I have a thing, and I want to tag it with a keyword or label. The "thing" is arbitrary. Assigning it a label puts it into an organizational system that supersedes it's functional organization.
- Labels should be global, if I were to search / filter by a label, I should be able to see across my organization and see all issues associated with that label, independent of where it's functionally categorized.
Concerns
Forcing globally, could cause redundancy:
- 4 labels show up with the same name?
- 4 labels with the same name are merged into 1, causing a growth of issues in issue boards seperated by group?
- are issue boards group wide?
Edited by 🤖 GitLab Bot 🤖