The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Are there any risks of using the shared project configuration function?

Vera Valshonok
Contributor
December 14, 2023

We are having a big, actively used project with lots of settings, shared with many customers (company -based/JSM).

When creating project, we want to choose an option to USE settings from this project to a new one. 

Are there any risk in it?

What will appear is new project and what won't? I saw that Forms are not moving to a new project for example.

Thanks!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Marc -Devoteam-
Community Champion
December 15, 2023

Hi @Vera Valshonok 

When creating a new project using another existing project to share settings, only the schemas will be used so:

  • Issue Type Scheme
  • Workflow Scheme
  • Issue Type Screen Scheme
  • Field Configuration Scheme
  • Permission Scheme
  • Notification Scheme
  • Security Scheme 

Not any of the following request types and the configuration of them, customer notifications, permissions itself, customers on the project, organisations.

Vera Valshonok
Contributor
December 19, 2023

Thanks! Where can I find exact info what will be shared and what not?

Vera Valshonok
Contributor
December 19, 2023

Not sure I understood your last paragraph what will be shared and what not?

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events