Extend guidelines on labels
Discussion
Labels in GitLab have historically been tightly coupled with Issues, Epics, and Merge Requests groupproject management. There are other use cases (Compliance Frameworks or Topics) in GitLab where users are creating elements to categorize objects that would benefit from using label the component.
Scoped labels are a sub-type of labels, and their usage is determined by the user. A scoped label is differentiated from a regular label by the contrasting colors on the left and right sides of the label. - Pajamas
Pajamas merely states that there is only a differentiation in the UI, but there is a unique feature tied to exclusivity in scoped labels for project management. Compliance Frameworks are currently using scoped labels just for visual flair, although it is not possible to apply more than one Compliance Framework to a project today.
When considering the scoped label
attribute, should this UI element always have exclusivity as a corresponding feature?