Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to remove first fieldvalue from jira align 'Multi Select List' custom field


Hello All,

Happy Friday!

Is there a way to remove the first field value from a 'multi select list' custom field? We created a multi select field at epic level and we made some changes to this field and we do not want this value to show up on our 600+ epics that we have. 



Thank you.

1 answer

1 vote
Tina Behers Community Leader Oct 08, 2021

@sachin gangam Unfortunately, no.  The first Option entered into the list, is (at this time) not able to be deleted as with other options in the list. 

However, if you have a NEW value to enter, you may EDIT the name of the old to be the new value...  although in my testing this will (erroneously) change the value to the new text on all existing epics that had the old value. 

In the images below Image 1 represents the " Old Value" = Thing 1 

Custom Field 1.PNG

If I update (Edit) The name so that the "New Value" = Thing 2 

When you change the text to Thing 2 - all Epics that previously were Thing1, become Thing 2 automatically. 

Custom Field 2.PNG


The best (and it's not good) work around that I have found it change the value for #1 to be DO NOT USE- then find all epics where custom field value = DO NOT USE 9using Enterprise insights or add the column in the Epics grid view page are the only ways to do this).  Update all Epics with the old value to a new value. 


I hope this helps! 

Thank you @Tina Behers  . I initially renamed it to 'None' , but we wanted to totally remove it, so users will not choose it from the dropdown, I can update the epics using import method and remove 'None' from all the epics and will rename it to something useful. Thanks again for your input.

Like Tina Behers likes this
Tina Behers Community Leader Oct 08, 2021

Sachin - based on my experience as a process engineer and Enterprise Architect, I would strongly advise against using "none".  Given that this will continue to exist beyond your initial clean up, it will be available for end users to continue to select. Which means continuous clean up....  

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events