We can see 1000+ labels in our board when we want to use one of our existing labels, why it is not limited per board.
My team must use one of our own defined labels, is it somehow possible to manage?
Another crazy thing is if I copy paste , since the drop down list is bit garbage & long ; if my copied label is somehow different (extra blank space or partial copied text or extra text) then congratulations I contributed by creating one new garbage label.
It is super annoying as an individual team member on top of added administration.
Is it technically feasible to limit it per board or can be restricted to users from creating new labels.
Thank you!
Hello @Suresh Yadav
This is because labels are being shown globally and you cannot limit it per board. That is also the main difference between components and labels. In your case, components would work better, however you would need to create different components per Jira space.
Hello @Suresh Yadav ,
Good day! Welcome to Atlassian community :)
Unfortunately there isnt a way to limit the label creation on board. However we have a feature request to restrict the label creation to certain group of users such as project admin etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Suresh Yadav
Labels are essentially a global "Wild West" by design. There isn’t a native setting to restrict them to a specific board or prevent users from creating new ones on the fly. Because they’re lightweight and site-wide, you’ll almost always run into typos and tags leaking in from other teams.
If you need an "official" or controlled list, I’d recommend switching to "Components" or a "custom select field" . Components are great because they’re scoped to your specific project and managed by admins, which keeps things much cleaner.
Essentially, labels are for flexibility, while components and select fields are for governance. If your team requires a strictly approved list, labels just aren't the right tool for the job.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for reaching out to the Atlassian Community. Please provide more details if possible!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.