Optional
boardsOptional
fieldDefines the payload for the fields, screens, screen schemes, issue type screen schemes, field layouts, and field layout schemes
Optional
issueThe payload for creating issue types in a project
Optional
notificationThe payload for creating a notification scheme. The user has to supply the ID for the default notification scheme. For CMP this is provided in the project payload and should be left empty, for TMP it's provided using this payload
CMP:"project": {
"pcri": "pcri:project:ref:new-project1",
"notificationSchemeId": "pcri:notificationScheme:id:10000",
...
}
TMP: "notification": {
"pcri": "pcri:notificationScheme:ref:notification1",
"name": "Simplified Notification Scheme",
"notificationSchemeEvents": [
{
"event": {
"id": "1"
},
"notifications": [
{
"notificationType": "CurrentAssignee"
},
{
"notificationType": "Reporter"
},
{
"notificationType": "AllWatchers"
}
]
},
{
"event": {
"id": "2"
},
"notifications": [
{
"notificationType": "CurrentAssignee"
},
{
"notificationType": "Reporter"
},
{
"notificationType": "AllWatchers"
}
]
},...
]
}
Optional
permissionThe payload to create a permission scheme
Optional
projectThe payload for creating a project
Optional
roleOptional
scopeThe payload for creating a scope. Defines if a project is team-managed project or company-managed project
Optional
securityThe payload for creating a security scheme. See https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
Optional
workflowThe payload for creating a workflows. See https://www.atlassian.com/software/jira/guides/workflows/overview\#what-is-a-jira-workflow
The specific request object for creating a project with template.