Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-12056

Bulk Edit for "Change Fix Version/s" multi-select field is addiditive, but replacement semantics is needed.

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

            [JRACLOUD-12056] Bulk Edit for "Change Fix Version/s" multi-select field is addiditive, but replacement semantics is needed.

            Tair Tidhar made changes -
            Component/s Original: Issue - Navigation [ 46635 ]
            Tair Tidhar made changes -
            Component/s New: Issue - Search - Frontend only [ 77950 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3153945 ] New: JAC Suggestion Workflow 3 [ 3655772 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336510 ] New: JAC Suggestion Workflow [ 3153945 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Eric S (Inactive) made changes -
            Component/s New: Issue Navigation [ 46635 ]
            Component/s Original: Issue Navigation & Search - Bulk Operations [ 46560 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2101372 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336510 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2063666 ] New: JIRA Bug Workflow w Kanban v6 [ 2101372 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1867594 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2063666 ]
            jonah (Inactive) made changes -
            Description Original: 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
            		 New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-12056].
              {panel}

            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
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-12056 [ JRASERVER-12056 ]

              Unassigned Unassigned
              38a17e3694df Steve Bachinsky
              Votes:
              30 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: