Random Request types while creating the project through API

[sankalp.khare]

We are creating a project in Jira Service Management using shared settings through the API. However, when the project is created via the API, default request types are appearing even though they do not exist in the reference (shared settings) project.

These request types also do not seem to have any connection with the shared settings project. We would like to understand which project settings are being referenced when these request types are created by default.

Additionally, what is the best approach to ensure that the request types from the shared project are copied exactly as they are?

[Tomislav Tobijas · Accepted solution]

Hi @sankalp.khare ,

Here's a list of entities that are shared when you create a new service space: Create and edit a service project 

As for copying request types, they may not always be copied exactly due to current platform limitations, and currently, there is no built-in way to guarantee that they are copied exactly as they are in the reference space when creating a new space via API.

There are two feature requests that relate to this:

• JSDCLOUD-1317: Ability to copy request types to another Service Management project. 
• JSDCLOUD-4276: Request type schemes 

As for the API you're using, I'm guessing it depends on the actual calls you're using. I've never built something like that, but as work types are global entities (when talking about company-managed spaces), there should be some attribute that you can set when 'copying' request types that determines which work type it is assigned to 👀

If you could share part of the API call that creates this part, we could take a look at it.

Cheers,
Tobi

[sankalp.khare]

Post 
curl --location 'https://companyname.atlassian.net/rest/api/3/project' \

--header 'Accept: application/json' \

--header 'Content-Type: application/json' \

atlassian.xsrf.token=845c573e29a441eab1d76924f1698dd9a544eb0f_lin' \

--data '{

"key": "CTP",

"name": "checking the project",

"projectTypeKey": "service_desk",

"leadAccountId": "Need_to_maintain_Account_id",

"description": " new testing___checking",

"assigneeType": "PROJECT_LEAD",

"url": "https://companyname.atlassian.net",

"avatarId": 10200,

"categoryId": 10000,

"workflowScheme": 10070,

"issueTypeScheme": 10185,

"issueTypeScreenScheme": 10036,

"fieldConfigurationScheme": 10068,

"permissionScheme": 10000,

"notificationScheme": 10000

}'

The IDs provided here for the example

This is the way I have created the project using shared settings