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

Retain values checkbox for Bulk Move should preserve versions or components based on version and components names

    XMLWordPrintable

Details

    Description

      Each project has different versions and components and therefore when moving issues between projects the versions and components will always be changed. We can make this option a bit more smart by letting JIRA check the version name and then change the versions and components based on name if the retain checkbox has been set.

      This gets tricky if more than one version/component has been selected on the issue, and a match is found for one of the selected versions/components. In this case should we:
      a) remove the version/component that does not have a version/component with the same name in the destination project
      b) remove the invalid version/component and replace it with the option entered by the user. In this case the values that do have a matching mapping in the destination project based on name will be kept
      c) completely replace the values with the ones entered during move.

      Attachments

        1. bulkmigration_mapping.png
          28 kB
          Felix Schmitz [Atlassian]
        2. bulkmove_retain.png
          75 kB
          Jeff Turner
        3. bulk-move-retain-3.11.png
          36 kB
          Ian Daniel [Atlassian]

        Issue Links

          details

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-20310 Update screenshots in documentation for Bulk Move with Versions/Components field

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-8894 'Retain' checkbox on versions in bulk move doesn't work

          • Medium - Medium priority issues
          • Closed
          is related to

          Suggestion - JRASERVER-15365 Bulk change, Move issues: Retaining does not work for a custom field with Version Picker

          • Closed

          Suggestion - JRASERVER-66699 Version Picker Field Does not Transfer

          • Gathering Interest
          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-18485 Update UI and Docs regarding misleading Retain Values on Bulk Move Issues

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              mtokar Michael Tokar
              anton@atlassian.com AntonA
              Votes:
              64 Vote for this issue
              Watchers:
              42 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: