You cannot manage labels centrally, it can only be done via issues. For example if you need to rename one you would have do a JQL to select all issues with the label, bulk edit them and add the new label, then bulk edit again to remove the old label.
Does that mean that once a developer adds a new Label to the list, it can not be removed, or edited? Maybe I am not reading this right, but that seems like an over site! I understand that an issues label can be changed, but if someone adds an offensive, or incorrect Label to the available list, then it's stuck in that list for good...
Run a query to find all the Issues across your entire jira instance with that label. Then you have to either do a bulk update to remove (but this will remove ALL labels). Or go through one by one and remove it.
If the label exist on a single issue in Jira it will show in the dropdown.
In regards to deleted labels still showing up as suggested labels – one cause of this is that Jira stores recently entered labels in your browsers local storage, which is then displayed in the "RECENT LABELS" section.
There is a ticket here to change the way that this behaves, but in the mean time this list can be manually cleared by deleting the
local storage item.
In Chrome this can be done by opening the browser Development tools, going to Application, then under "Local storage" in the sidebar selecting your jira url, and finally selecting the key noted above and pressing Delete.
seems that for every solution we (the end users) need to by some additional plugin @Mikael Sandberg did your PO do a benchmarking about the other apps? I suggest to take a look into azure DevOps... you don't need to buy additional plugins in order to list the stories under feature to review the feature progress, if you are creating a metric dashboard for your stakeholders you can include the average velocity of the team (or teams) you can even decide the shape/format of your dashboard... you don't need to buy an additional plugin to embed graphs/widgets from jira to confluence... anyway, there are lot of gaps that jira has. it's a shame
@Karla Bernal I was legit saying this yesterday, it's like Jira is the Spirit Airlines of ITSM/Project software. Everything is extra. This is particularly frustrating when using the expensive ITSM ($45/u/m) product only to find it doesn't have standard features included and then to be further let down that the devs are aware and have been for years yet are refusing to implement because of reasons. *Shakes fist at the sky*
Hello Mikk Olli,
Jira native 'Labels' field allows everyone to create new labels anytime. This often results in a mess of options.
We built an App that not only allows to clean up (edit, merge, delte) Jira native 'Labels' field globally or on a project level, but also to create 'Label Manager' own custom field type that allow to predefine allowed labels globally or for each project.
This allows project admins to manage their the options themselves without help from global Jira admins. (Like components)
Also you can use the label as checklist by assigning traffic light colors indepent on each issue.
Hope I could help you
Jira does not have built-in option to manage labels.
Fortunately, there are apps/add-ons that enable this feature. Our app for Jira Cloud provides extensive label management features, please try it using this link:
If you are using Jira Server/DC, there are some other options in the Marketplace. You can find them using this link 👉 Atlassian Marketplace