Question about configuring settings for a new project

[Colleen]

I need to create a new project that has most of the configurations as other projects that all share a bunch of settings. Probably the only major thing I need to change is the workflow, and I know if I associate a new workflow to the scheme, it will change the workflow for all the other projects as well. (is this correct?) So I was thinking I could copy the workflow scheme and associate the new workflow with it and assign to the project. My question is, should I keep the other configurations (issue types, permissions, screens...) or make copies of them and reassign if I need to adjust later? Not sure at this point, but I might need to edit these down the line and I don't want the changes to affect other projects. Any advice on how to proceed? 

[Deepanshu Natani · Accepted solution]

Hi @Colleen 

You can create a project which will be sharing configurations with other existing projects.

Once the project is created, you can create a new workflow scheme for this particular project with the appropriate workflow and then associate it with this project. This will make sure that going forward, if you make any change to the workflow for this project, that won't impact your other projects.

Coming to the other configurations like screens schemes, etc, you can keep the, shared for the time being, and in the future, if the need arises for having a change in this, you can create a separate scheme at that time.

[Colleen]

Ok yes this makes sense and seems like the appropriate course of action. Thanks!