For new project with shared configuration, will changing setting on new project affect the old one?

[Daniel Byrne]

Hi all,

I'm a total newbie so forgive the basic question! If I create a new project that shares configurations of an existing project, will making a change in the new project affect the existing projects configuration?

Specifically, I wish to test possible changes to screens etc that are currently being used, without it affecting the already established and running project. I have created a new project only available to myself, which shares configuration with the existing project, and want to keep any changes to one separate from the other.

Does sharing the configuration forever link the 2 projects (so changes to one affects the other)? I just want to play around with a few things without messing up the existing project for the entire team! Thanks for any help!

[Dirk Ronsmans · Accepted solution]

Hi @Daniel Byrne and welcome to the community!

If this is a shared configuration then that indeed means that the same configuration is used by multiple projects.

So a change on the settings will be reflected in both projects.

The idea here is to not have to maintain multiple projects if they have the same setup.

If you want to test something you might be better of to copy the existing configuration and linking the copies and not use a shared configuration.

[Robert Wen_Cprime_]

Welcome, @Daniel Byrne . Welcome to the Atlassian Community!

Yes, if you change a screen, workflow,  or scheme that is shared, the change propagates to all projects that share that screen or scheme.

You can create the change and then associate with one project (but not the other).  That will "break" the shared configuration for that item (screen, workflow, or scheme) between the two projects.

[Joseph Chung Yin]

@Daniel Byrne -

In addition to what @Dirk Ronsmans mentioned, here are some exceptions - Example

1) You are using custom fields and only want it to show up in project A but not in project B.  In this case, you can control the field context so it is only setup for project A and not expose it to project B.  Using this setup, you can add the fields in the same screen configuration scheme (shared by project A and project B), so those fields will not be available/visible to project B's issue screens.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.