-
Suggestion
-
Resolution: Obsolete
-
Enterprise version... I believe other details are N/A to this issue.
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When we attempt to perform a bulk edit on several cases to "Change the Fix Version/s", the behavior is that the field values provided in the bulk edit are additive – meaning that the values just get added to the existing values in the multi-selector for the "Fix Version/s" field and we can't get the old values removed. Is this expected behavior? If so, this is a problem when we have a number of cases that we planned to fix for one version and need to bulk change them to fix for a different version.
Ideally, there should be a "retain original values" checkbox to allow the semantics to be either additive or replacement.
Thanks, Steve
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
- was cloned as
-
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-12056] Bulk Edit for "Change Fix Version/s" multi-select field is addiditive, but replacement semantics is needed.
For those of you, who find similar challenges related to other fields in JIRA, please make sure to check our latest feature addition described as a solution to JRA-24118.
Cheers,
Bartek
JIRA Product Manager
This is no longer an issue in JIRA, it has been obsolete for a while now.
By researching support cases, I have noticed that this is reported to not occur since 5.2.4 and we have tested that it doesn't occur in 6.2.1 either. Therefore, I am resolving this issue as obsolete.
As mentioned by barisacar in the previous comments adding the capability of optionally doing an additive operation rather than a replacement is still open at JRA-13456, as some customers would like to have the option to choose between an addition or a replacement operation.
Regards,
Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].
+1
This has a significant impact on our sprint planning process. In the Greenhopper Planning tab, we used to be able to drag items from one version to another. But now we can't even do that, because if you drag it into another version, it simply applies the "Fix Version" to both versions (ie: additive). Even direct changes to the Edit screen keep the old version.
Warren Poon
added a comment - - edited +1
This has a significant impact on our sprint planning process. In the Greenhopper Planning tab, we used to be able to drag items from one version to another. But now we can't even do that, because if you drag it into another version, it simply applies the "Fix Version" to both versions (ie: additive). Even direct changes to the Edit screen keep the old version. 
Baris Acar
added a comment - I thought the opposite was the case - in fact there's a Jira item (JRA-13456) to enable additive semantics rather than replacement...
Baris Acar
added a comment - I thought the opposite was the case - in fact there's a Jira item ( JRA-13456 ) to enable additive semantics rather than replacement... This case was updated to include the points of this comment. Would delete comment if I could.
Steve Bachinsky
added a comment - - edited This case was updated to include the points of this comment. Would delete comment if I could. 
Still don't work on cloud