You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We tag JIRA issues with labels to make it easier to find related issues across projects.
One of the labels we use is the customer's name. Problem is that companies sometime change their name. Now to the question: How can we change the name of a JIRA label in use?
I don't want to go through all issues and update them manually so is there an easier way to simply rename an existing label?
We use JIRA Ondemand.
There's a decent "Bulk Modify" workaround:
It should be in the "tools" menu when you have run a search for a set of issues or run a saved filter. Should be near the top right with a cog, tools or ...
Thanks for information. One more thing i just wanted to know if we are particular about Capital letter /Small letter . for Example if i have to Replace low high med with Low High Med then search criteria will pull both. So is there any way to choose just lower letter word i mean specific word /label and Replace it will Normalized word for better readability. Please let me know
This workaround is sorely lacking IMO because any filters that refer to the label will be broken after applying this "fix."
This is the main reason I think Atlassian should consider implementing a real solution, which would be supporting renaming of labels. After all, the main reason for labels is so that you can search on them, and the most useful searches are those that get saved, dashboarded, etc (filters).
Hi @Eric ,
I agree, you should take filters into account when "renaming" a label using bulk edit. In fact, it doesn't stop there: Labels could also be used in workflows (Conditions, Validators, some Post Functions) and even Automations.
If I had the originally mentioned problem – a company changed their name and now I need a new label – I would still use bulk edit. However, instead of removing the old label and adding the new label, I would just add the new label. This way, older filters etc. would still work.
Personally, I believe renaming a label is a totally different use-case: You would rename a label when someone misspelled a label, so that your filter works again. Like "login" vs "log-in" for example. Which incidentally is one of the features that almost all label apps in the marketplace have – including ours.
As for Atlassian implementing a real solution, that not only updates the text of a label, but also all filters and so on: I would not count on it. Considering how widespread JQL queries and hence label-based searches are within not only Jira, but also all the different available apps, it seems to me like an almost impossible task. The user experience would definitely be worse, if all filters keep on working after changing a label, but now your ScriptRunners scripts are broken.
Using two labels instead of one (in the "just add a new label" suggestion) means everyone now has to track and maintain two labels for one situation. Yes, another workaround, but harder on everyone than just having the ability to rename labels.
As far as worrying about ScriptRunnner and other external tools: Doesn't this problem exist any time you integrate multiple software tools? The same problem will happen if I use the bulk edit/replace workaround suggested earlier. But I think people understand when they do their own integration like this, they have have to maintain the consistency within the queries themselves. That does not sound like a reason to not provide a feature users are requesting.
Personally, I believe there are many use cases for changing labels--not just one. Certainly more than the several identified in this topic.
Oh yes, adding a second label definitely is a sub-optimal work-around. In my mind, the best solution from the start would have been a multi-select custom field, because then you could natively rename any options. And if you wanted to integrate external tools, you could target an option's ID instead of the text – you cannot do that with labels, as far as I know.
Speaking from an app vendor's perspective, when a label is changed we never know the intend behind that change: Was it the wrong label or is a label being renamed? Should be we update the filters our users have stored or not? I think that would result in a lot of inconsistent behaviour between different apps. But hey, I might be very wrong here.
In the end, I personally like labels as an organizational tool in Jira and anything that makes that better would be welcomed by me.
If it's a common operation, you have a bit of a problem with your users. Might be worth fixing the problem at source.
That would only lead you to a small number of edge-cases though.
I understand that from a developer's point of view (the JIRA team), this would be a low priority because (a) it doesn't happen THAT often and (b) there is a not-TOO-onerous workaround. But from a user's point of view (multiple JIRA users who have posted here, including myself) it happens sometime and we would like to be able to directly perform the operation, so I "voted" for it.
I'm not sure what your point is, though... Are you part of the JIRA team voting to not implement this? Or are you saying you never have the problem so you don't care if it gets implemented?
That's fine, but I think you have to understand that software can't do everything.
I'm not an Atlassian, and I'm not saying this is something I would not want to do if I were. But I've got a list of things I would like Jira to do, and this is the sort of thing that is very very low down it, as you say, because it doesn't happen often and the workaround is trivial.
If you think it's important, have a look at https://jira.atlassian.com - that contains all the feature requests.
The community here generates some, and discusses them, but has zero weight when it comes to prioritisation. You should find the request and vote for it - that's the main input Atlassian use from customers.
I think this feature is never gonna make it to the software :
1-The workaround is easy
2-I always discourage my user to use label to manage important classification is Jira. Because of mistyping, it's not reliable enough. Use something else, like components or a custom property with a dropdown...
This would typically require a backend database change, so I can think of 2 alternatives for OnDemand.
1) Submit a request to support. They may be willing to update the data table and reindex JIRA for you - https://answers.atlassian.com/questions/141323/is-it-possible-to-rename-a-label
2) Use the "Bulk Modify" feature to search for issues with "CompanyZ" and add the label "CompanyZee". This will remove all existing labels from those issues!
We should use Find /Replace option by selecting the respective Column /Field. Specially it will help for Labels and comments to make more standardized.. Is there any way we export the data in csv - Correct the details and upload as Update the the Issues . Please let me know.
This is old thread but there does not seem to be proper solution yet.
I am happy to inform you that we have released a new add-on which allows renaming labels very easily:
This is currently available for Jira Cloud. It allows you to:
- View all labels in one place
- Number of issues under a label
- Rename or change label (which is reflected in all issues)
If you find any bugs or have questions, feel free to contact us.