Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-12056

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • 5.2.4
    • Bulk Operations
    • Enterprise version... I believe other details are N/A to this issue.
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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

          Form Name

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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3058866 ] New: JAC Suggestion Workflow 3 [ 3678769 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2615765 ] New: JAC Suggestion Workflow [ 3058866 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2582633 ] New: Confluence Workflow - Public Facing v4 [ 2615765 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2360312 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2582633 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2127796 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2360312 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2090522 ] New: JIRA Bug Workflow w Kanban v6 [ 2127796 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 888147 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2090522 ]
            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 Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-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 relates to JRACLOUD-12056 [ JRACLOUD-12056 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

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

                Created:
                Updated:
                Resolved: