What does "Share settings with an existing project" mean and how does it work?

Gabe Cz
Contributor
December 3, 2024

Hi

So if my understanding is correct, if I create a new project (call it PRJ-B), and check that option and pick an existing project (call it PRJ-A), then when I change anything in PRJ-A the settings will be applied to PRJ-B is that so?

It would be great to have a sandbox/dev option so to change something in a dev version of a project (PRJ-DEV), test things out and say "apply settings to main project (PRJ-A) but isn't the option above for something like that? Not really I think...

I dug a little bit, but couldn't find the article or more info on the option "Share settings with an existing project"

3 answers

2 votes
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 3, 2024

When you use the "Share settings with an existing project" it means that you will share the configurations of issue types, workflows, screens, fields, permissions, and notifications. The use case you specified above would not work because if you make a change in project B it would automatically take effect in project A as well. You can learn more about shared configurations in this KB

For your use case you would need to use an app, or manually recreate the changes between projects. There are a handful of apps in the Marketplace that can do this.

1 vote
Susan Waldrip
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 3, 2024

Hi @Gabe Cz , thanks for posting your question to the Community! You are correct that selecting that checkbox when creating a new project will apply all the same settings/configuration of the existing project to your new project. Once your new project is created, you can leave those settings as-is and if you make a change to either project, it will affect the other, too. If you don't want that, you can make copies of the schemes, workflows, etc. of the existing project and change the names for the new project (and remember to change the schemes to reflect the new names); that way you can make changes to either project but it will only affect the project you changed.

As for copying configuration changes and issues from sandbox/dev to production or vice-versa, you can try using the JSM Copy Product Data feature (Admin > Settings > Data management > Copy product data) OR the Manage sandboxes feature (same page as Copy Product Data) to see if that meets your needs. These features are nice but don't give you the control, granularity, or information about your data that Revyz Data Manager for Jira , Salto Configuration Manager for Jira, Rewind, or another backup/restore/cloning app available in the Atlassian Marketplace. 😊

1 vote
Harshit Grover
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 3, 2024

Hi @Gabe Cz ,

 

When creating a new project using the "Shared Configuration" option, the schemes and configurations of the new project will mirror those of the existing project.

Please note that if you do not make the configurations of the existing project specific to that project after the new project is created, any changes made to PRJ-A will also apply to PRJ-B.

Let me know if you have any questions or need further clarification.

Regards,
Harshit Grover

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events