• Approval
  • Customer
  • Customer Request
  • Customer Transition
  • Jira Service Management Application
  • Organization
  • Organization Service Desk
  • Portals
  • Queue
  • Queue Settings
  • Request Attachment
  • Request Type
  • Request Type Permissions
  • Service Desk
  • Service Desk Customer
  • application-properties
  • applicationrole
  • attachment
  • avatar
  • cluster
  • comment
  • component
  • configuration
  • customFieldOption
  • customFields
  • dashboard
  • email-templates
  • field
  • filter
  • group
  • groups
  • groupuserpicker
  • index
  • index-snapshot
  • issue
  • issueLinkType
  • issuesecurityschemes
  • issuetype
  • issuetypescheme
  • jql
  • licenseValidator
  • monitoring
  • mypermissions
  • mypreferences
  • myself
  • notificationscheme
  • password
  • permissions
  • permissionscheme
  • priority
  • priorityschemes
  • project
  • projectCategory
  • projects
  • projectvalidate
  • reindex
  • resolution
  • role
  • screens
  • securitylevel
  • serverInfo
  • session
  • settings
  • status
  • statuscategory
  • terminology
  • universal_avatar
  • upgrade
  • user
  • version
  • websudo
  • workflow
  • workflowscheme
  • worklog
  • Assets - AQL
  • Assets - Analytics
  • Assets - Archived Objects
  • Assets - Attachments
  • Assets - Comments
  • Assets - Icons
  • Assets - Index Configuration
  • Assets - Object
  • Assets - Object Archive
  • Assets - Object Attribute
  • Assets - Object Connected Tickets
  • Assets - Object Restore
  • Assets - Object Schema
  • Assets - Object Type
  • Assets - Object Type Attribute
  • Assets - Progress
  • Assets - QR Code
  • Assets - Status Types
Server
Jira Service Management / Reference / REST API

issue

Postman Collection
OpenAPI
Operations
POST/api/2/issuePOST/api/2/issue/archivePOST/api/2/issue/bulkGET/api/2/issue/createmeta/{projectIdOrKey}/issuetypesGET/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}GET/api/2/issue/pickerGET/api/2/issue/{issueIdOrKey}PUT/api/2/issue/{issueIdOrKey}DEL/api/2/issue/{issueIdOrKey}PUT/api/2/issue/{issueIdOrKey}/archivePUT/api/2/issue/{issueIdOrKey}/assigneePOST/api/2/issue/{issueIdOrKey}/attachmentsGET/api/2/issue/{issueIdOrKey}/commentPOST/api/2/issue/{issueIdOrKey}/commentGET/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}/pinGET/api/2/issue/{issueIdOrKey}/editmetaPOST/api/2/issue/{issueIdOrKey}/notifyGET/api/2/issue/{issueIdOrKey}/pinned-commentsGET/api/2/issue/{issueIdOrKey}/propertiesGET/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}/remotelinkPOST/api/2/issue/{issueIdOrKey}/remotelinkDEL/api/2/issue/{issueIdOrKey}/remotelinkGET/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}/restoreGET/api/2/issue/{issueIdOrKey}/subtaskGET/api/2/issue/{issueIdOrKey}/subtask/movePOST/api/2/issue/{issueIdOrKey}/subtask/moveGET/api/2/issue/{issueIdOrKey}/transitionsPOST/api/2/issue/{issueIdOrKey}/transitionsGET/api/2/issue/{issueIdOrKey}/votesPOST/api/2/issue/{issueIdOrKey}/votesDEL/api/2/issue/{issueIdOrKey}/votesGET/api/2/issue/{issueIdOrKey}/watchersPOST/api/2/issue/{issueIdOrKey}/watchersDEL/api/2/issue/{issueIdOrKey}/watchersGET/api/2/issue/{issueIdOrKey}/worklogPOST/api/2/issue/{issueIdOrKey}/worklogGET/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