POST /rest/api/2/project

Creates a project based on a project type template, as shown in the following table:

Project Type KeyProject Template Key
businesscom.atlassian.jira-core-project-templates:jira-core-simplified-content-management, com.atlassian.jira-core-project-templates:jira-core-simplified-document-approval, com.atlassian.jira-core-project-templates:jira-core-simplified-lead-tracking, com.atlassian.jira-core-project-templates:jira-core-simplified-process-control, com.atlassian.jira-core-project-templates:jira-core-simplified-procurement, com.atlassian.jira-core-project-templates:jira-core-simplified-project-management, com.atlassian.jira-core-project-templates:jira-core-simplified-recruitment, com.atlassian.jira-core-project-templates:jira-core-simplified-task-tracking
service_deskcom.atlassian.servicedesk:simplified-it-service-management, com.atlassian.servicedesk:simplified-general-service-desk-it, com.atlassian.servicedesk:simplified-general-service-desk-business, com.atlassian.servicedesk:simplified-external-service-desk, com.atlassian.servicedesk:simplified-hr-service-desk, com.atlassian.servicedesk:simplified-facilities-service-desk, com.atlassian.servicedesk:simplified-legal-service-desk, com.atlassian.servicedesk:simplified-analytics-service-desk, com.atlassian.servicedesk:simplified-marketing-service-desk, com.atlassian.servicedesk:simplified-design-service-desk, com.atlassian.servicedesk:simplified-sales-service-desk, com.atlassian.servicedesk:simplified-blank-project-business, com.atlassian.servicedesk:simplified-blank-project-it, com.atlassian.servicedesk:simplified-finance-service-desk, com.atlassian.servicedesk:next-gen-it-service-desk, com.atlassian.servicedesk:next-gen-hr-service-desk, com.atlassian.servicedesk:next-gen-legal-service-desk, com.atlassian.servicedesk:next-gen-marketing-service-desk, com.atlassian.servicedesk:next-gen-facilities-service-desk, com.atlassian.servicedesk:next-gen-general-it-service-desk, com.atlassian.servicedesk:next-gen-general-business-service-desk, com.atlassian.servicedesk:next-gen-analytics-service-desk, com.atlassian.servicedesk:next-gen-finance-service-desk, com.atlassian.servicedesk:next-gen-design-service-desk, com.atlassian.servicedesk:next-gen-sales-service-desk
softwarecom.pyxis.greenhopper.jira:gh-simplified-agility-kanban, com.pyxis.greenhopper.jira:gh-simplified-agility-scrum, com.pyxis.greenhopper.jira:gh-simplified-basic, com.pyxis.greenhopper.jira:gh-simplified-kanban-classic, com.pyxis.greenhopper.jira:gh-simplified-scrum-classic

The project types are available according to the installed Jira features as follows:

To determine which features are installed, go to Jira settings > Apps > Manage apps and review the System Apps list. To add Jira Software or Jira Service Management into a JIRA instance, use Jira settings > Apps > Finding new apps. For more information, see Managing add-ons.

Permissions required: Administer Jira global permission.

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
leadAccountId String No

The account ID of the project lead. Either lead or leadAccountId must be set when creating a project. Cannot be provided with lead.

lead String No

This parameter is deprecated because of privacy changes. Use leadAccountId instead. See the migration guide for details. The user name of the project lead. Either lead or leadAccountId must be set when creating a project. Cannot be provided with leadAccountId.

description String No

A brief description of the project.

url String No

A link to information about this project, such as project documentation

issueTypeScreenScheme Integer No

The ID of the issue type screen scheme for the project. Use the Get all issue type screen schemes operation to get a list of issue type screen scheme IDs. If you specify the issue type screen scheme you cannot specify the project template key.

permissionScheme Integer No

The ID of the permission scheme for the project. Use the Get all permission schemes resource to see a list of all permission scheme IDs.

categoryId Integer No

The ID of the project's category. A complete list of category IDs is found using the Get all project categories operation.

fieldConfigurationScheme Integer No

The ID of the field configuration scheme for the project. Use the Get all field configuration schemes operation to get a list of field configuration scheme IDs. If you specify the field configuration scheme you cannot specify the project template key.

assigneeType String No

The default assignee when creating issues for this project.

Possible values:

  • "UNASSIGNED"
  • "PROJECT_LEAD"
avatarId Integer No

An integer value for the project's avatar.

projectTypeKey String No

The project type, which defines the application-specific feature set. If you don't specify the project template you have to specify the project type.

Possible values:

  • "software"
  • "business"
  • "service_desk"
name String Yes

The name of the project.

workflowScheme Integer No

The ID of the workflow scheme for the project. Use the Get all workflow schemes operation to get a list of workflow scheme IDs. If you specify the workflow scheme you cannot specify the project template key.

key String Yes

Project keys must be unique and start with an uppercase letter followed by one or more uppercase alphanumeric characters. The maximum length is 10 characters.

notificationScheme Integer No

The ID of the notification scheme for the project. Use the Get notification schemes resource to get a list of notification scheme IDs.

issueTypeScheme Integer No

The ID of the issue type scheme for the project. Use the Get all issue type schemes operation to get a list of issue type scheme IDs. If you specify the issue type scheme you cannot specify the project template key.

issueSecurityScheme Integer No

The ID of the issue security scheme for the project, which enables you to control who can and cannot view issues. Use the Get issue security schemes resource to get all issue security scheme IDs.

projectTemplateKey String No

A predefined configuration for a project. The type of the projectTemplateKey must match with the type of the projectTypeKey.

Possible values:

  • "com.atlassian.servicedesk:simplified-general-service-desk"
  • "com.atlassian.servicedesk:simplified-sales-service-desk"
  • "com.pyxis.greenhopper.jira:gh-simplified-scrum-classic"
  • "com.atlassian.servicedesk:simplified-hr-service-desk"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-process-control"
  • "com.atlassian.servicedesk:simplified-it-service-management-basic"
  • "com.atlassian.servicedesk:next-gen-hr-service-desk"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-project-management"
  • "com.atlassian.servicedesk:next-gen-general-it-service-desk"
  • "com.atlassian.servicedesk:next-gen-finance-service-desk"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-task-"
  • "com.atlassian.servicedesk:next-gen-legal-service-desk"
  • "com.pyxis.greenhopper.jira:gh-cross-team-template"
  • "com.atlassian.servicedesk:simplified-facilities-service-desk"
  • "com.atlassian.servicedesk:simplified-blank-project-business"
  • "com.pyxis.greenhopper.jira:gh-simplified-agility-scrum"
  • "com.pyxis.greenhopper.jira:gh-simplified-agility-kanban"
  • "com.atlassian.servicedesk:next-gen-analytics-service-desk"
  • "com.atlassian.servicedesk:simplified-legal-service-desk"
  • "com.atlassian.servicedesk:next-gen-facilities-service-desk"
  • "com.atlassian.servicedesk:next-gen-sales-service-desk"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-document-approval"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-recruitment"
  • "com.atlassian.servicedesk:simplified-it-service-management"
  • "com.atlassian.servicedesk:simplified-it-service-management-operations"
  • "com.pyxis.greenhopper.jira:gh-simplified-basic"
  • "com.atlassian.servicedesk:simplified-design-service-desk"
  • "com.atlassian.servicedesk:next-gen-it-service-desk"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-procurement"
  • "com.pyxis.greenhopper.jira:gh-cross-team-planning-template"
  • "com.atlassian.servicedesk:simplified-marketing-service-desk"
  • "com.atlassian.servicedesk:simplified-external-service-desk"
  • "com.atlassian.servicedesk:simplified-finance-service-desk"
  • "com.atlassian.servicedesk:simplified-analytics-service-desk"
  • "com.atlassian.servicedesk:next-gen-general-service-desk"
  • "com.atlassian.servicedesk:next-gen-design-service-desk"
  • "com.pyxis.greenhopper.jira:gh-simplified-kanban-classic"
  • "com.atlassian.servicedesk:simplified-internal-service-desk"
  • "com.atlassian.servicedesk:simplified-halp-service-desk"
  • "com.atlassian.servicedesk:next-gen-general-business-service-desk"
  • "com.atlassian.servicedesk:simplified-blank-project-it"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-lead-tracking"
  • "com.atlassian.servicedesk:simplified-general-service-desk-it"
  • "com.atlassian.jira-core-project-templates:jira-core-simplified-content-management"
  • "com.atlassian.servicedesk:simplified-general-service-desk-business"
  • "com.atlassian.servicedesk:next-gen-marketing-service-desk"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.