Support for Server products ended Feb. 15, 2024. Learn what this means for you.

Server

Jira Service Management / / REST API

issue

Postman Collection

Operations

POST/api/2/issue POST/api/2/issue/archive POST/api/2/issue/bulk GET/api/2/issue/createmeta/{projectIdOrKey}/issuetypes GET/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}GET/api/2/issue/picker GET/api/2/issue/{issueIdOrKey}PUT/api/2/issue/{issueIdOrKey}DEL/api/2/issue/{issueIdOrKey}PUT/api/2/issue/{issueIdOrKey}/archive PUT/api/2/issue/{issueIdOrKey}/assignee POST/api/2/issue/{issueIdOrKey}/attachments GET/api/2/issue/{issueIdOrKey}/comment POST/api/2/issue/{issueIdOrKey}/comment GET/api/2/issue/{issueIdOrKey}/comment/{id}PUT/api/2/issue/{issueIdOrKey}/comment/{id}DEL/api/2/issue/{issueIdOrKey}/comment/{id}PUT/api/2/issue/{issueIdOrKey}/comment/{id}/pin GET/api/2/issue/{issueIdOrKey}/editmeta POST/api/2/issue/{issueIdOrKey}/notify GET/api/2/issue/{issueIdOrKey}/pinned-comments GET/api/2/issue/{issueIdOrKey}/properties GET/api/2/issue/{issueIdOrKey}/properties/{propertyKey}PUT/api/2/issue/{issueIdOrKey}/properties/{propertyKey}DEL/api/2/issue/{issueIdOrKey}/properties/{propertyKey}GET/api/2/issue/{issueIdOrKey}/remotelink POST/api/2/issue/{issueIdOrKey}/remotelink DEL/api/2/issue/{issueIdOrKey}/remotelink GET/api/2/issue/{issueIdOrKey}/remotelink/{linkId}PUT/api/2/issue/{issueIdOrKey}/remotelink/{linkId}DEL/api/2/issue/{issueIdOrKey}/remotelink/{linkId}PUT/api/2/issue/{issueIdOrKey}/restore GET/api/2/issue/{issueIdOrKey}/subtask GET/api/2/issue/{issueIdOrKey}/subtask/move POST/api/2/issue/{issueIdOrKey}/subtask/move GET/api/2/issue/{issueIdOrKey}/transitions POST/api/2/issue/{issueIdOrKey}/transitions GET/api/2/issue/{issueIdOrKey}/votes POST/api/2/issue/{issueIdOrKey}/votes DEL/api/2/issue/{issueIdOrKey}/votes GET/api/2/issue/{issueIdOrKey}/watchers POST/api/2/issue/{issueIdOrKey}/watchers DEL/api/2/issue/{issueIdOrKey}/watchers GET/api/2/issue/{issueIdOrKey}/worklog POST/api/2/issue/{issueIdOrKey}/worklog GET/api/2/issue/{issueIdOrKey}/worklog/{id}PUT/api/2/issue/{issueIdOrKey}/worklog/{id}DEL/api/2/issue/{issueIdOrKey}/worklog/{id}

POST

Create an issue or sub-task from json

Creates an issue or a sub-task from a JSON representation. The fields that can be set on create, in either the fields parameter or the update parameter can be determined using the /rest/api/2/issue/createmeta resource. If a field is not configured to appear on the create screen, then it will not be in the createmeta, and a field validation error will occur if it is submitted. Creating a sub-task is similar to creating a regular issue, with two important differences:

the issueType field must correspond to a sub-task issue type (you can use /issue/createmeta to discover sub-task issue types), and
you must provide a parent field in the issue create request containing the id or key of the parent issue. The updateHistory param adds the project that this issue is created in, to the current user's project history, if set to true (by default, the project history is not updated). You can view the project history in the Jira application, via the Projects dropdown.

Request

Query parameters

updateHistory

boolean

Request bodyapplication/json

Issue update bean

fields

object

historyMetadata

HistoryMetadata

properties

array<EntityPropertyBean>

transition

TransitionBean

update

object

Responses

Returns a link to the created issue.

application/json

IssueCreateResponse

POST/api/2/issue

curl

Node.js

Java

Python

PHP

curl --request POST \
  --url 'http://{baseurl}/rest/api/2/issue' \
  --user 'email@example.com:<api_token>' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json'

POST

Archive list of issues

Archives a list of issues.

Request

Query parameters

notifyUsers