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

Ability to Create Versions / Components in destination project with Bulk Operations

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.

      We'd like the ability to chose weather or not to copy/create versions and components when bulk moving issues to a new project. Currently, they need to be manually created in the destination project before Bulk Operations.

      Details:

      Currently in Jira Software Cloud, when you MOVE an issue (from the issue itself in the MORE menu) that has Versions or Components to a new project - if the destination project does not have these Versions or Components users can either ADD new values or map to existing within the destination project.

      Moving One Issue from issue More (...) menu

       

      However, when using Bulk Operations from Filters, even for only one issue, you MUST map to existing values in the destination project. Based on the details on the screen - it almost seems like the values would be created if "retain" is selected.

       

      Moving ONE issue with Bulk Operations

            Unassigned Unassigned
            47564f916a4b Ben W
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: