How not to let bulk change overwrite existing values fields (Component, affected version)

Hi All

Components and affect versions are multi select fields i.e. can hold more than one values in it.

Now if we are using bulk change feature to add a set of issues with a certain component we find that the old values in them gets overwritten.

e.. say Issue A has component X already in it. and i am bulk changing a set of issues which includes Issue A to add component Y to it. After bulk change i find that Issue A only has component Y andcomponent X is overwritten.

How can we prevent this?

1 answer

1 accepted

This widget could not be displayed.

I'm afraid you can't at the moment.

I am sure there is an issue raised about this in Atlassian's Jira, but it's not in my bookmark list. Possibly because I'm pretty sure it was raised in Jira 2.x, if not earlier...

Thanks Nic. I guessed so. Is there any workaround to this that you may think of?

Script bulk changes externally is about the only thing I've done - a SOAP call to get the current values, work out what needs updating and perform an edit. (I'd use REST or the script-runner nowadays)

Hi Nic,


I notice Affects version field is not seen during bulk change. I'd need to do bulk update with different value for 'Affects version' this not possible with JIRA->Bulk change option? Am using JIRA 7.3.4.

thanks for your reply.

The original answer is out of date, you can now add values to some fields, rather than overwrite.

If a field is not on the list of things you can bulk-edit, then the most likely reason is that it is not on the "edit" screen.

yeah it is not on the edit screen. is there other way to have such fields also bulk-edited?


To be able to do something in bulk-edit, you have to be able to do it to the issues. 

You'll need to add the field to the screen before you can bulk-edit them.

Yes we will need to add the field required to be it possible to bring in new fields to the edit screen? If yes, will you help me with steps to achieve pls? Thx


Go check the project that the issues live in.  Have a look at the project admin screen, where you'll find the "issue type screen scheme".  Work your way down into that, looking for the "edit" screens for the issue types you need to change.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

262 views 5 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you