Share settings with an existing project? (JSM Cloud)

[Catrine Lundström]

Hi,

Can anyone prove a list of what exactly is copied when you create a new Jira Service Management (Cloud) project, IT Service Management and choose "Share settings with an existing project"?

BR

Catrine

[Walter Buggenhout · Accepted solution]

Hi @Catrine Lundström,

Don't shoot me if I am forgetting something ;-), but as far as I know the following configurations are shared:

• issue types
• workflows
• screens
• fields
• permissions
• notifications

Your new project will actually use the same configuration schemes as the project you selected as your source.

On top of that some additional settings (from the project details page) are copied:

• project category
• project lead
• default assignee

Hope this helps!

[Catrine Lundström]

Thanks!

Can you (from the top of hour head) say something that is NOT shared that you find missing?

BR

Catrine

[Walter Buggenhout]

Hi @Catrine Lundström,

Yes, definitely. I would say the two most important things you'll need to set after creating the project are permissions and a board.

Setting permissions means adding your project users to appropriate roles. If you track your project through a team board (I mean a board set up to track the work for multiple projects), then this might not be necessary. If you want a scrum or kanban board just for your project, then that's also something you'll need to add yourself. 

[Yatish Madhav]

Thanks for the feedback @Walter Buggenhout  - Do you perhaps know of any doccos that exist that shows what is not / cannot be shared?

I also noticed that Project description, URL, Project Avatar, Versions and Components are not copied/shared when Shared settings is set.

Via the API I am able to do the same as done via that checkbox BUT cant get the Notification Scheme (https://community.developer.atlassian.com/t/assign-notification-scheme-to-project-via-api/66640) set or the Project Avatar, Versions and Components

[Kenny Dick]

@Yatish Madhav How did you get the "Share settings with an existing project" checkbox working via the API?

[Yatish Madhav]

@Kenny Dick I did so in multiple steps and multiple calls to the APIs and did some error handling/fallbacks too but here is the gist of it:

• get original project details (for name,description, URL, Project Avatar)
• generate a new project key and name
• get original project notification scheme
• create new project
• get original project issue type screen scheme
• delete new project issue type screen scheme - optional
• assign project issue type screen scheme
• get original project workflow scheme
• delete new project workflow scheme - optional
• assign project workflow scheme
• get original project issue type scheme
• delete new project issue type scheme - optional
• assign project issue type scheme
• get original project permission scheme
• delete new project permission scheme - optional
• assign project permission scheme
• get original project field configuration scheme
• delete new project field configuration scheme - optional
• assign project field configuration scheme
• get original project issue security scheme
• delete new project issue security scheme - optional
• assign project issue security scheme
• manually copy automation rules or assign if multi project - I wihs Atlassian API allows for interacting with the automation rules

Hope this helps. Thank you

[Kenny Dick]

Thanks so much @Yatish Madhav this is great! Thanks for sharing.