• 6
    • 10
    • 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.

      Atlassian Update - 31 March 2015

      Hi everyone,

      This issue is a duplicate of JRA-12059; however, due to the high number of votes we will leave it open. Please refer to our response on that issue.

      Regards,
      Dave Meyer
      Product Manager, JIRA Platform

      If there is a group of issue types you have to carry out for each new Version again, it's not possible to duplicate these issues with a new status for the new Version.

            [JRASERVER-6404] Bulk clone issues, updating certain fields

            Using the power scripts app , you can create issue template automations and solve this use case. You can bulk copy projects, issues, attachments and even create a template of issues to launch and reuse quickly. (more info)

            Monte Montoya added a comment - Using the power scripts app  , you can create issue template automations and solve this use case. You can bulk copy projects, issues, attachments and even create a template of issues to launch and reuse quickly.  (more info)

            We have jusst launched a new plugin for this, compatible from 6.3.6
            Check and evalutate on: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro

            Best
            Lars Broden

            Lars Broden added a comment - We have jusst launched a new plugin for this, compatible from 6.3.6 Check and evalutate on: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugin.pro.BulkClonePro Best Lars Broden

            Zac added a comment -

            I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

            Zac added a comment - I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

            Zac added a comment -

            I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

            Zac added a comment - I am also using the Zephyr for Jira plugin, and go through a similar process for Test Case Management. Cloning and moving test cases to a standard repository for future use (before archiving a project) is currently a very painful and manual process. A bulk clone feature would remedy this pain. It would also likely benefit other workflows such as potentially creating a standard set of tasks/sub-tasks, that could be cloned and applied component of work at any time during planning.

            We would find this feature very useful for our test team. We are using Zephyr and our work involves a pattern of very similar projects and test cycles. What we would like to do is to have standard test cases defined and held in the system (e.g. in a dummy Test Repository project) and then be able to find and filter them based on component, label or some such and then apply a bulk operation to clone them into the project where they are required. Having a "clone into other project" option under the bulk operations list would be exactly what we need for this.

            Richard Caton added a comment - We would find this feature very useful for our test team. We are using Zephyr and our work involves a pattern of very similar projects and test cycles. What we would like to do is to have standard test cases defined and held in the system (e.g. in a dummy Test Repository project) and then be able to find and filter them based on component, label or some such and then apply a bulk operation to clone them into the project where they are required. Having a "clone into other project" option under the bulk operations list would be exactly what we need for this.

            BulkClone plug-in doesn't meet our requirement as it depends on a filter and not a custom selected issue list. It is not always possible to create a filter to select the issues we want to clone

            SHANTI JACOB added a comment - BulkClone plug-in doesn't meet our requirement as it depends on a filter and not a custom selected issue list. It is not always possible to create a filter to select the issues we want to clone

            Lars Broden added a comment - Well, You could always try out this free plugin: https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugins.bulkclone.BulkClone

            Can anyone please comment on when "Bulk Clone" functionality is scheduled to be made available in JIRA? We are using JIRA version 6.0.3 and I don't see any mechanism to bulk clone JIRA issues and change only a field or two. I was hoping in Bulk Operations, just like Bulk Edit, Bulk Assign etc., Bulk Clone will be available too but did not find it

            Jiten Kothari added a comment - Can anyone please comment on when "Bulk Clone" functionality is scheduled to be made available in JIRA? We are using JIRA version 6.0.3 and I don't see any mechanism to bulk clone JIRA issues and change only a field or two. I was hoping in Bulk Operations, just like Bulk Edit, Bulk Assign etc., Bulk Clone will be available too but did not find it

            Bob Swift added a comment - - edited

            As a workaround, JIRA CLI will do this for download provided you have the Clone Plus Plugin installed - this is what allows you to change project and/or update fields other than the summary field.

            --action cloneIssues --toProject "XYZ"  --description "Bulk clone example"  --search 'project = ABC and summary ~ "xyz-*"  '
            

            For OnDemand, you can only clone to the same project and change the summary using the same technique. Since you can't install the plugin for OnDemand, you have to settle for the limited support available with the built-in clone action.

            Bob Swift added a comment - - edited As a workaround, JIRA CLI will do this for download provided you have the Clone Plus Plugin installed - this is what allows you to change project and/or update fields other than the summary field. --action cloneIssues --toProject "XYZ" --description "Bulk clone example" --search 'project = ABC and summary ~ "xyz-*" ' For OnDemand, you can only clone to the same project and change the summary using the same technique. Since you can't install the plugin for OnDemand, you have to settle for the limited support available with the built-in clone action.

            ClarkN added a comment -

            Agree - need the ability to clone in bulk in either Jira Core or OnDemand, please!

            ClarkN added a comment - Agree - need the ability to clone in bulk in either Jira Core or OnDemand, please!

              Unassigned Unassigned
              d4df88337a3c Volker Weck
              Votes:
              244 Vote for this issue
              Watchers:
              128 Start watching this issue

                Created:
                Updated: