Create a new project by 'create with shared configuration' from a existing project.

[Kristy]

when creating a new project(named A) by 'create with shared configuration' from a existing project(named B), the project A settings will copy from existing project.

I want to know: If I make change for the settings of either project A or existing project. Will it affect each other?

For example, if i change the issuetype settings of project A, will the change also happen to B?

[Gor Greyan]

Hi @Kristy

Welcome to the Atlassian Community!

When you create a project using "Create with shared configuration", the new project shares the same configuration schemes as the source project rather than creating independent copies. This includes items such as the workflow scheme, issue type scheme, screen scheme, field configuration scheme, permission scheme, and notification scheme.

As a result, if you modify one of these shared schemes, the changes will be reflected in both projects (and any other projects using the same scheme).

For example, if Projects A and B share the same Issue Type Scheme and you add or remove an issue type from that scheme, both projects will see the change.

On the other hand, project-specific settings, such as project details, components, versions, project roles, and project-specific automation rules, are not shared, so changes to those only affect the individual project.

If you want Project A to evolve independently from Project B, you'll first need to associate it with its own configuration schemes (or create copies of the existing ones) before making changes.

Also, you can find this documentation helpful.

https://confluence.atlassian.com/servicedeskcloud/create-and-edit-a-service-project-1097175899.html

[Marc -Devoteam-]

Hi @Kristy 

Welcome to the community.

Create a project with a shared configuration will use the same schemes as the project you used as base for your new project.

So if you make changes to the schemas, these are used by both projects, this will impact both.

On each schema you can see which project (spaces) use this particular scheme.

If you don't want this to happen, then you will have to create a new scheme of the required type and associate this with the related space.

Also check this article on schemas, Configurations-overview-Understanding-Jira-schemes 

[Gabriela]

Hi @Kristy, welcome to the community.

"Create with shared configuration" sets project A up on the very same schemes project B already uses: the workflow scheme, issue type scheme, screen scheme, field configuration scheme, plus the permission and notification schemes. Each one is a single shared object, so editing it reaches every project associated with it. That works in both directions. Change the shared issue type scheme while you're in A and B moves with it, and the same happens if you change it from B. So yes, your issue-type example would hit both projects.

To let one project diverge, copy the scheme (Settings > Issues > Issue type schemes > Copy), edit the copy, and associate only that project with it. Project-level things like components, versions, the lead and the project name stay independent.

https://confluence.atlassian.com/adminjiraserver/defining-a-project-938847066.html