Still, the bug is marked as fixed and closed in a version that is exclusively available OD. This doesn't make much sense for 90% of customers, which are not using the OD versions.... is like saying "case closed, solved on my own machine"... not identical but you got the idea.

I think that bugs should never be marked as fixed only with "OD" versions, if this is supposed to be included in the unreleased yet "6.4", why we are not seeing this in the Fix Versions?

circusdog, this is planned to be available for Server deployments with the upcoming version of JIRA 6.4 - coming really soon.

Cheers,
Bartek

@Bartek - It looks like this is currently fixed for cloud customers only. Can you please tell us which version of the server offering will contain the fix?

Great news, everyone. The solution to this request is provided as a fix for another JAC request: JRA-24118.

I am therefore closing this one as "Fixed".

Thanks for your comments, and votes.

Cheers,
Bartek
JIRA Product Manager at Atlassian

When used for the 'Fix Version' field, I like to think of this functionality as giving the option to "preserve version history" or "replace all values"

This makes sense to apply to multi-select fields in general though, & options are always nice.

Even a generic variable as a value like current version to denote to keep the previous values - whatever makes the most sense for the UI & workflow.

I'm also interrested in Bulk add to Component/s.

I agree 100%

Agreed. The bulk edit is essentially broken because of that. Adding a new version has become a very painful operation.

What is Atlassian's response to this?

I see several issues created and many votes and watchers. JIRA's bulk change functionality is broken and can do a lot of damage to the database by bulk editing multi-value fields. We are running into this on updating versions, adding (or trying to) a new label to issues with existing labels, selecting a value on a multi-checkbox to issues with existing values checked. It wipes out all existing data!

Example:

I have a multi-check box called follow-up with values "include in release notes", "create knowledge base article", "update training", etc. If I search for a group of issues and want to add the "include in release notes" in bulk, it wipes out any existing checked values.

The bulk change function needs a Add or Replace option for all multi-value fields. Without this, we can't allow people to use it, and it's worthless for multi-value fields.

Thanks,
Robert

This is something we need desperately also.
Can Atlassian please provide an update on this.

Thanks