Existing projects

[Cassandra Hughes]

Is it possible to use a project I created as a template?

[Trudy Claspill · Accepted solution]

Hello @Cassandra Hughes 

Welcome to the Atlassian community.

What elements of the existing project do you want to reuse when you create a new project?

- The configuration (i.e. fields, screens, issue types, workflows, etc)

- The users assigned to project roles

- The issue in the source project

- The configuration of a board associated with the project

What type of project is it? Get that information from the Type column on the View All Projects page under the Projects menu.

The suggestion provided by @Ollie Guan is for sharing just the first bullet above, and works only when the source and destination projects are both Company Managed projects. When that option is used, the configuration becomes shared between the two projects. A change to the configuration elements in one will affect the other. This option doesn't create a copy of the configuration elements that then belongs only to the new project.

The configurations for Team Managed projects cannot be shared.

Jira doesn't provide a native method to share the other elements listed in the bullets above, but there are third party apps that can handle at least some of those options. If you want those are you open to considering a third party app?

[Cassandra Hughes]

Thank you for your response. The project I want to use as a template is a company managed project. The configuration is what I am looking to duplicate for another project. Most of the elements will be the same. More than half of the issue types, all the workflows, screens, and fields. It would just be assigned to a different set of users. I guess I was just looking for an easier way to jump the line on the amount of work I would need to do to create another one of these projects.

[Trudy Claspill]

Following @Ollie Guan 's suggestion to make the new project Share the configuration of an existing project gets you part way there.

When using that option the new project and existing project would share all the same Schemes, so changes to any of them would affect both projects.

If you want to customize some of the configuration elements for the new project then you would have to create separate Schemes for those elements.

Depending on how many schemes (and scheme child elements) you want to customize for the new project you would need to make a choice between:

- creating the new project with the Share Configuration option, then manually copying/creating the schemes/elements you want to be able to customize and associating those to the new project.

- creating the new project without the Share option so that all new baseline schemes are created for the new project, and then associating just the schemes you want to reuse from the template project to the new project.

[Ollie Guan]

Hi @Cassandra Hughes ,

Share settings with an existing project when you create new project.

[Luka Hummel - codefortynine]

Hi @Cassandra Hughes and welcome to the community!

To effectively duplicate your project setup, consider using our app Deep Clone for Jira. This app allows you to clone entire projects with its Project Clone feature, including configurations like workflows, issue types, screens, and fields, with or without sharing configurations between projects.

You can even assign different users and customize fields specifically for your new project with the Field Editor feature. This is a great way to streamline your setup and save time.

[Cassandra Hughes]

Oh this sounds interesting. What does this app cost? Will it allow moving or merging individual projects from sandbox to prod instances? 

[Luka Hummel - codefortynine]

Hi @Cassandra Hughes

You can check the pricing on the marketplace page here. 

Yes, you can use Deep Clone to clone whole projects or only the issues of a project between sandbox and production instances. To do that, you need to configure the Instance Clone feature on the target and source instances. You can read more on that here.