'Save as template' function on a space/project - does it tie back to the original space/project?

[Melissa Bradford _C_]

I have a space/project in Jira (let's call it ProjectA) that has a complicated workflow and specific work type tickets.
I want to create a separate space/project (Project Z) with the exact same workflow and ticket types so that I can test a 3rd party integration and ensure that my pipelines can run and update the tickets as required but I don't want this in any way to update anything in Project A.
I know that I can click the 'save as template' button on the Project A space to create a 'custom template' but I need to ensure that there are no ties to Project A and that Project Z would have the same configuration (workflow, ticket types etc) but be completely separate space/project?

[Trudy Claspill]

Hello @Melissa Bradford _C_ 

I tried out this feature to create a custom project template (available only in Enterprise plans) and then created a new project from the template. Here's what I found.

For the new project made from the template the following items were copied and given a new name:

• Workflows
• Workflow Scheme
• Screens
• Screen Schemes
• Issue Type Screen Scheme

The following did NOT have copies made. The new project is using the same ones as the project from which the template was created.

• Issue Type Scheme
• Priority Scheme*
• Permission Scheme
• Issue Security Scheme
• Notification Scheme*
• Field Configurations*
• Field Configuration Scheme*

For the items above marked with an asterisk I was using default from the system in the source project. I don't know what would've happened if I had customized versions there.

[Trudy Claspill]

So if you modified the elements in the second list that would affect the original project and the new project.

You would need to examine the workflows for any customizations that named the source project explicitly. I don't think those would be automatically changed when the workflows are copied for creation of the new project.

[Staffan Redelius]

Hi @Melissa Bradford _C_ and welcome

I am assuming you are talking about Company managed projects.

When you create the new project you can choose to create the project based on a existing project, Just point out Project A in the create space wizard and you will get a new project that shares the same workflows, issuetypes etc as Project A.

Just bare in mind that these projects will share configurations/schemas so any changes you do in project Z will affect every project sharing the schemas.

You can decouple the projects by making copies of the existing schemas, do the modification you need and assign the new schema to Project A.

 Best regards,
/Staffan