What happens when "Share settings with an existing project" with original Project?

[eric.spink]

Hi,

We are looking to create a new project based off of another project we have? I notice you can do this with the "Share settings with an existing project". But if I read correctly from various answers. If you make a change on the new project, it will apply the change to the original project. 

Is this true?

Is there way to simply use one project as a base and then when changes happen on the new project, it doesn't effect the original project?

Thank you,

[Trudy Claspill · Accepted solution]

Hello @eric.spink 

Welcome to the community.

If you use the Share Settings option, the new project will be created and associated to the same Schemes used in the original project.

If at a later date you make a change to any of those Schemes, those changes affect all projects that use the changed Scheme.

If you need to make changes to a Scheme for a new project, I suggest this process:

1. Create the new project using the "Share settings" option.

2. For the Scheme that needs to be changed for the new project, make copies of the source Scheme (and any child elements of it, like copying the Workflow Scheme and each Workflow in the scheme).

3. Make changes to the copies.

4. Update the new project to use the new scheme (the copies you have just updated).

That is the only way to use "Share settings" and then allow projects to diverge from those shared settings at a later date.

[Bastian Stehmann]

Hi @eric.spink ,

Welcome to the community. 

You are right, if you create a project with a shared configuration, the used configuration schemes like workflows, screens, ... are shared between the projects.

So if you change something like a workflow, it will affect both projects. This is to keep all projects of one "type" in sync.

If you want to change something in only one project, you could create a copy of only that scheme that you would like to change and apply that scheme to the project. 

If you want to have it distinct from the beginning, you have to copy all schemes manually and apply them, there is no built-in way to create a copy of the whole project configuration. 

[Yatish Madhav]

Thanks for the question and Answer @eric.spink  and @Trudy Claspill - this is a nice functionality for Jira/Atlassian to introduce.

Something like "Duplicate settings with an existing project" so that the new project has a new set of configurations associated with it BUT is created from the source/original projects configurations.

[Trudy Claspill]

Hello @Yatish Madhav 

I encourage you to check if that is already a Suggestion in the Atlassian backlog, and to create a new Suggestion if it is not.

https://jira.atlassian.com/secure/Dashboard.jspa

[John Funk]

Hi Eric - Welcome to the Atlassian Community!

It depends on what you mean by making a change on the new project. Projects are linked to multiple schemes such as workflows, permissions, notifications, etc. These are the things that get shared between the new and old project. So if you need to make a change to the work, yes, it would effect the original project.

But you can also simply make a copy of the original workflow, make your changes, and then attach the new workflow to the new project. So there is the ability to make changes fairly easily if you need to.