Details

    • Type: New Feature New Feature
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 3.5.1
    • Fix Version/s: None
    • Component/s: Project Management
    • Labels:
      None

      Description

      Please add a feature that would allow JIRA to clone Projects.

        Issue Links

          Activity

          Hide
          Michael Oliver added a comment -

          So here are my IMHO thoughts inline on the questions Jeff poses above:

          What would cloning projects involve?
          Cloning projects allows users to utilize JIRA in a application lifecycle management sense in that they can determine what feature items can be associated with typical "project" that parallels their SDLC to some extent. Each release cycle can automattically generate a "basic project" or template with all the typical issues automatically populated with default values that can be customized based on what is going on in the next release. This would help us in terms of software release where the development is more like an assembly line such as in information systems related to clinical research orgs (CRO). Same basic software is released multiple times for multiple clients, some with customization some not.

          • Cloning just the project info (obviously the key would need to change)
            At the very least the project info and base level issues. Perhaps a "batched, clone and move" event could create a fresh project from an existing "template" project. Perhaps maybe something more elegant if needed.
          • Cloning associated permission, notification, workflow schemes?
            Make this configurable. Ideally perms, notification and workflow is abstracted somewhat from the project level objects so that projects could "subscribe" to perm, notification and workflow schemes already in existence, or possibly subscribe to new ones. The batch clone and move idea could potentially just grab what ever linkages exist in the template project if the user selects this level of cloning.
          • Cloning associated custom fields?
            Make this configurable. Ideally custom fields are portable enough to be repository material that can be drawn into a particular project. The batch "clone and move" idea could potentially just grab what ever is in the template project if the user selects this level of cloning.

          What are the problems that you're experiencing, that you think project cloning will solve?

          Some of us want to be able to create an SDLC that is more like an assembly line VS. product leveling, or extension. So, more like banging out cookie-cutter versions of the same system with minor configuration changes vs a whole new version of an exsting product.

          JIRA would be awesome to manage this, but needs to be able to repeat projects with base configuration without having to "hand create" the basic beginning state (by adding issues etc...) of the assembly line prior to a starting a new cycle.

          Show
          Michael Oliver added a comment - So here are my IMHO thoughts inline on the questions Jeff poses above: What would cloning projects involve? Cloning projects allows users to utilize JIRA in a application lifecycle management sense in that they can determine what feature items can be associated with typical "project" that parallels their SDLC to some extent. Each release cycle can automattically generate a "basic project" or template with all the typical issues automatically populated with default values that can be customized based on what is going on in the next release. This would help us in terms of software release where the development is more like an assembly line such as in information systems related to clinical research orgs (CRO). Same basic software is released multiple times for multiple clients, some with customization some not. Cloning just the project info (obviously the key would need to change) At the very least the project info and base level issues. Perhaps a "batched, clone and move" event could create a fresh project from an existing "template" project. Perhaps maybe something more elegant if needed. Cloning associated permission, notification, workflow schemes? Make this configurable. Ideally perms, notification and workflow is abstracted somewhat from the project level objects so that projects could "subscribe" to perm, notification and workflow schemes already in existence, or possibly subscribe to new ones. The batch clone and move idea could potentially just grab what ever linkages exist in the template project if the user selects this level of cloning. Cloning associated custom fields? Make this configurable. Ideally custom fields are portable enough to be repository material that can be drawn into a particular project. The batch "clone and move" idea could potentially just grab what ever is in the template project if the user selects this level of cloning. What are the problems that you're experiencing, that you think project cloning will solve? Some of us want to be able to create an SDLC that is more like an assembly line VS. product leveling, or extension. So, more like banging out cookie-cutter versions of the same system with minor configuration changes vs a whole new version of an exsting product. JIRA would be awesome to manage this, but needs to be able to repeat projects with base configuration without having to "hand create" the basic beginning state (by adding issues etc...) of the assembly line prior to a starting a new cycle.
          Hide
          Gum Shoes added a comment -

          We have been using the http://blogs.onresolve.com/?p=57 plugin for JIRA 3.12.2 but it no longer works with 3.13.2.
          Has anyone had any luck using Jelly for this?

          Show
          Gum Shoes added a comment - We have been using the http://blogs.onresolve.com/?p=57 plugin for JIRA 3.12.2 but it no longer works with 3.13.2. Has anyone had any luck using Jelly for this?
          Hide
          Gum Shoes added a comment -

          The author of http://blogs.onresolve.com/?p=57 has fixed it to work with 3.13.x now, it works again for me.

          Show
          Gum Shoes added a comment - The author of http://blogs.onresolve.com/?p=57 has fixed it to work with 3.13.x now, it works again for me.
          Hide
          Hien Dang added a comment -

          Thanks Gum Shoes!!

          I've just installed the 'Copy Project plugin' from http://blogs.onresolve.com/?p=57. It works like a gem.
          Does exactlly what I was looking for - which is just basically to create a new Project based on a 'Project template'.

          I created a new Project category = ' Project Templates'
          Created new - Project templates - eg, External Client Project Template & Internal Client Project Template.
          configured the standard schemes / security / workflows etc.
          added a standard list of Components, Versions etc

          Show
          Hien Dang added a comment - Thanks Gum Shoes!! I've just installed the 'Copy Project plugin' from http://blogs.onresolve.com/?p=57 . It works like a gem. Does exactlly what I was looking for - which is just basically to create a new Project based on a 'Project template'. I created a new Project category = ' Project Templates' Created new - Project templates - eg, External Client Project Template & Internal Client Project Template. configured the standard schemes / security / workflows etc. added a standard list of Components, Versions etc
          Hide
          Roy Krishna [Atlassian] added a comment -

          Hi All,

          We are currently tidying up our public JIRA instance so I will close this issue as we are tracking this request on the main linked issue: JRA-7020.

          Cheers,
          Roy

          Show
          Roy Krishna [Atlassian] added a comment - Hi All, We are currently tidying up our public JIRA instance so I will close this issue as we are tracking this request on the main linked issue: JRA-7020 . Cheers, Roy

            People

            • Assignee:
              Unassigned
              Reporter:
              chuong
            • Votes:
              27 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: