Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-12059

Bulk Copy (clone+move) Issues to Multiple Projects



    • UIS:
    • Support reference count:
    • Feedback Policy:
      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 - 22 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap.

      There is a workaround, though, that might be used for the specific use case defined in the description. It involves JIRA Importers Plugin (or JIM for short), which is available for both Cloud and Server deployments of JIRA. JIM allows for issues to be imported from CSV format (also available for regular JIRA users - not only Admins) and JIM's wizard includes a step where user select the project he/she wants the issues are to be imported into. So the workaround will be to export the desired issues into CSV file using Issue Navigator and then import them back into another project using JIM.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Dave Meyer
      Product Manager, JIRA Platform

      Original request description:

      I'm working on rolling out JIRA to a Big 10 University in the U.S. We anticipate the potential to have hundreds or possibly thousands of projects in our installation. One of the features we are keen on being able to offer our faculty is the ability to create a series of tasks organized into milestones (versions) such as phased assignments, research projects, etc. Ideally each instructor will be able to create task collections in a "master" course template, and clone out entire filter sets (including relevant issues and versions) to a collection of other projects belonging to their students. At the beginning of the course, the instructor could bulk copy these assignments and tasks out to each participant student's personal time management project, and they'd each have a unique copy of the tasks, organized into version milestones. Right now, I envision this will involve the following:

      1. The ability to create a project with tasks tied to given milestones. This functionality exists in the present version of JIRA (3.7.2)
      2. The ability to bulk copy (clone and move) an entire project milestone, including all relevant issues, to a list of projects. This feature does not presently exist.
      3. The possibility to deny the ability described in item 2 above to a specific list of users on the server.

      I am willing to build this custom feature myself, but will need to purchase a source license first. However, the functionality might warrant a place in the default JIRA installation.

      The advantage of being able to do this in a default installation of JIRA is that it would simplify multi-project installations for all Open Source communities.

      EXAMPLE: all new projects need to perform basic project set-up chores (all administrivia you need to do to start an Open Source project, for example:

      • creating username on the appropriate servers,
      • setting up your ssh public keys,
      • mailing list tasks,
      • web site,
      • source repository publication,
      • adding developers and managing permissions,
      • producing unit tests,
      • documentation,
      • first release

      All of these common tasks could be grouped into a "Getting Started" milestone that server admins could clone out to all new projects. We used to run into this problem at the CodeHaus all the time. The Apache software foundation also has a long list of things that all new projects must complete in order to become an official TLD. These tasks should be able to be auto-cloned wholesale to one or more existing projects from a master template.

      I think having a case study on how to tie JIRA-based task management into the traditional academic enterprise would significantly increase the academic interest in this product. I saw some other issues out there that sort of batted this concept around, but nothing definitive or even that descriptive. I can't estimate how long this might take to implement, but welcome any suggestions or feedback from the JIRA development team.


          Issue Links



              saintx Alexander Saint Croix
              250 Vote for this issue
              125 Start watching this issue