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

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

XMLWordPrintable

    • 1
    • 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 tasks 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, Irwin

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

            Gosia Kowalska added a comment -
            Atlassian Update – 22 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 22 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

            Leos Leos added a comment -

            Our use case is to have such release strategy:

            versions: 1.0, 1.1, 1.2, Alfa, Beta, Gamma

            We work on 1.0. We start on Alfa build and we set fixVersion to Alfa, Beta, Gamma. When finished, I want to set fixVersion to 1.0, if it was missing.
            Later we start to work on 1.1. Again I want to track partial progress. I do not want to create new version for each build, so I recycle Alfa, Beta and Gamma. But they contain defects from version 1.0!

            I realized that I can only ADD new fixVersion with bulk action. I cannot unset / replace fixVersion. Please address this JIRA issue. Thank you.

            Leos Leos added a comment - Our use case is to have such release strategy: versions: 1.0, 1.1, 1.2, Alfa, Beta, Gamma We work on 1.0. We start on Alfa build and we set fixVersion to Alfa, Beta, Gamma. When finished, I want to set fixVersion to 1.0, if it was missing. Later we start to work on 1.1. Again I want to track partial progress. I do not want to create new version for each build, so I recycle Alfa, Beta and Gamma. But they contain defects from version 1.0! I realized that I can only ADD new fixVersion with bulk action. I cannot unset / replace fixVersion. Please address this JIRA issue. Thank you.

              Unassigned Unassigned
              3f927f2ac844 Sanjay Dewal
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: