What do we need to do to get useful labels across the Atlassian product space?

[Scott Boyden]

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).

[Jean Horn]

Hi @Scott Boyden !

I completely feel your pain on this, label sprawl is a classic headache for almost every growing Jira instance! When anyone with edit permissions can create labels on the fly, it doesn't take long before typos and variants (FCC, FCCU, fccu) completely dilute their value for searching and reporting.

While Atlassian hasn't implemented a native "Create Labels" permission node yet, here are a few practical ways community members manage and govern labels effectively:

1. Switch to Custom Select/Multi-Select Fields: If you need strict governance, custom fields (like a Multi-Select or Select List) allow Jira Admins to maintain a controlled vocabulary. Only admins can add new options, preventing silent creation of duplicate values.
2. Use Apps for Label Management: If you rely heavily on the flexibility of labels, marketplace apps like Label Manager or Label Bot allow admins to merge, rename, bulk delete, and monitor duplicate labels across projects.
3. Automate Cleanup with Automation for Jira: You can set up automation rules to auto-replace common misspellings or variants (e.g., automatically replacing fccu or Fluidized Cat with a standard FCCU label upon issue update).

Your proposed permission node idea is a solid and clean feature request. I'd definitely encourage upvoting existing feature requests around label governance so the product team can track customer demand!

Hope this gives you some good paths forward!

[Dan Breyen]

Hi @Scott Boyden looking at Atlassian's Jira Site I found JRACLOUD-60543 which is requested to restrict who can create labels.

I would suggest voting for and watching that for updates.  Feel free to comment on it as well.

Hope that helps.

[Scott Boyden]

Thanks!  My search didn't find the open ticket -- only ones that they had rejected.  

Voted! 

We would be happy if they want to keep the labels field as an uncontrolled placeholder and added a new field.

[Lucas Knorr]

Hi @Scott Boyden

as Jean already mentioned, since Jira itself does not provide any mechanism to restrict label creation, the best way to establish governance around labels is by using a 3rd-party plugin. 

With the latest release of Label Manager for Jira, you can now also have more control over Jira’s native labels by defining label rules and therefore allow/disallow specific labels on a project level.(Note I am from codecentric, the vendor of the app). 

Alternatively, you could implement an external script that periodically fetches your work item data and corrects or updates labels that don’t comply with your label rules.

If you decide to go down that route, I’d be happy to help you identify the required API endpoints.