Shared configuration in Jira software
Asked by Sanjen Bariki:

Hi Team,

I just want to know, If I am creating a project via shared configuration in the Jira software then Which data will not copy?

Like Components and versions, Instead of this are there any other things which will not copy the values?

Regards,

Sanjen


Answers:
author: Mayur Jadhav
body: Hi [@Sanjen Bariki](/t5/user/viewprofilepage/user-id/4993263) ,

That's correct it won't copy the Components, Version along with its values and Issue Security Scheme and Board.

comments: author: Sanjen Bariki
body: Hi [@Mayur Jadhav](/t5/user/viewprofilepage/user-id/4290135) ,

Apart from this, Do you think anything you have missed..?

Please check again, I think also more points.

Regards,

Sanjen


author: Mayur Jadhav
body: obviously issue won't be copy so sprint data and repots also will not be copied and users added to the project role will not except groups added to project role.


author: Sanjen Bariki
body: Hi [@Mayur Jadhav](/t5/user/viewprofilepage/user-id/4290135) ,

Yes, Thats what i want to know.

Like, I created one new projects via the Shared configuration but i saw the project roles copied in the notification scheme.

Can you please confirm, I saw the project role in the notification scheme But Is it copied the members in the roles..?

If I changed the project roles members in the project, Is it affects the another project..?

Could you please clarify the concept..?

Regards,

Sanjen


author: Wolfgang -Litew8 GmbH-
body: Hi [@Sanjen Bariki](/t5/user/viewprofilepage/user-id/4993263)

based on the documentation of 'Create project with shared configuration' the following and only the following is shared among projects when you create them with shared configuration:

* issue types
* workflows
* screens
* fields
* permissions
* notifications

Every thing else, just like you mentioned is not shared. We therefore built an app [**'Project Templates for Jira'**](https://marketplace.atlassian.com/apps/1230303) (**free** for you as you are under 10 users) that does allow to **create custom project templates** which also can be configured to share:

* Project description
* Project category
* Project URL
* Project lead
* Project default assignee
* Clone **components** from a project or predefine new components
* Clone **versions** from a project or predefine new versions
* Clone **project role actor assignment** from another project
* Create a basic **Kanban/Scrum board**
* Issue security scheme
* Clone existing **issues** or predefine issues  
  Including their Epic/Task/Subtask hierarchy

comments: author: Sanjen Bariki
body: Hi [@Wolfgang -Litew8 GmbH-](/t5/user/viewprofilepage/user-id/5059701) ,

Thanks Brother, But If I added anything in the Project role members after creating a new project then Is it affect the other project which is created by the configuration.

Regards,

Sanjen


author: Uche
body: Hi [@Sanjen Bariki](/t5/user/viewprofilepage/user-id/4993263)

No it won't be affected. Those project roles that appear like they have copied over are probably the default roles that appear whenever a new project is created on your instance.

Any changes you make to the roles/users will not have any affect on the other project in the shared scheme. As mentioned above by the other contributor the only thing that will be shared between the two projects is:

* issue types
* workflows
* screens
* fields
* permissions
* notifications

Hope this helps.


author: Wolfgang -Litew8 GmbH-
body: [@Sanjen Bariki](/t5/user/viewprofilepage/user-id/4993263)

As clarification, there are project permission schemes, and the people tab.

The **project permission scheme** maps individual users/groups/project roles to individual permission ('Create Issue') inside the project.

The **people tab** maps individual user/groups to project roles.

The **permission scheme** can be shared among multiple projects, meaning that any changes to them will affect all project that it is associated. Any changes to the people tab, will only affect the individual project.

Therefore, the**best practice** is, to**only map project roles inside the permission scheme.** This allows individual projects to manage their own permission by assigning individual users to project roles which will not affect other projects.  

The topic is quite complicated and it takes some time to wrap your head around it. Here is a link to the [official documentation](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/) that might help.


Tags: cloud

jira-software