Want to replace value of dropdown field by new value, it should change values on all existing tasks

[Pavan]

Hello Team,

Thanks in advance.

In our jira we have dropdown field (name=Release) and having values (mount, abs, sec).

I want to replace <mount> value with new value <Enact>.

I have many tasks in jira who all are having Release field value as <mount>, want to replace everywhere in jira.

Please suggest some possible solution

[Nic Brough _Adaptavist_ · Accepted solution]

Log in as an admin and go to Admin -> Issues -> Custom fields

Find "release" in the list of fields and use the menu to  the right to go to "contexts and default values".

Inside the context you are using, you will see the current list of options.   Edit <mount>, changing its name to <enact>

That's it - you've renamed the option, so it will be shown as <enact> everywhere it is currently used.

You may find some filters will need to be updated - your people may need to change clauses such as "and release = mount" to "and release = enact"

[Kagithala Babu Anvesh]

Hi @Pavan 

Before updating check the custom field is only used for this project. If multiple projects using this. 

You may need to context the field and apply the contested to other projects.

Go to custom fields 

Edit options 

Rename it 

And re index jira. 

Re index takes time depending upon your total issues in jira

[Radek Dostál]

If this is a single-select field, you could filter out the issues you want to update and do a bulk edit on top of them - just updating the field's value.

If this is a multi-select field, you could download a .csv with the columns 'Issue Key', 'Release', modify the values, and do an issue update with that .csv upload (this option requires you to have global Jira Admin permission and to understand how .csv updates work - we can elaborate on the steps).

Those would be the out of box options to do such updates.

If you are however trying to just change the option 'mount' to 'Enact' for all issues everywhere then you can just rename the option through Custom Fields (again, need to be a global admin for this) - that will rename it on all issues across the whole instance, without you needing to do any updates.