Problem: Label creation in Jira is an uncontrolled side effect of issue editing. Any user who can edit an issue can silently create a new label. Over time this produces duplicate, misspelled, and variant labels that are impossible to merge or clean up at scale.
Real example from our instance: FCC, FCCU, Cat Cracker, Fluidized Cat, Fluidize Cat, fccu — six labels representing one concept, created organically by different users. There is no way to detect duplicates on creation, no way to merge them, and no way to prevent recurrence.
Labels are a powerful cross-cutting classification tool. We use them to bridge Jira with personal productivity tools and other enterprise systems. But without governance, they degrade into noise and lose that value entirely.
Proposed Fix
Add a single new permission node: "Create and Edit Labels"
Slot it into the existing Project Permission scheme alongside Create Issues, Edit Issues, etc.
Users without this permission can apply existing labels but cannot create new ones
Admins assign the permission to a controlled group (e.g., project admins, team leads)
This is not a redesign. It fits entirely within the existing permission framework. The engineering surface area is small.
Why this matters: Components already offer controlled vocabularies — but they are rigid, hierarchically flat, and require admin overhead to maintain. Labels offer the flexibility that Components lack. There is currently nothing in the Atlassian toolset that provides both flexibility and governance. This single permission node closes that gap.
(Yep: I had Rovo help with this summary write-up hoping that since it is part of the Atlassian it would use key words and phrases to elevate the need. And yes, Atlassian has replied to similar label-management requests in the past with a "Won't Do" response).
