POST /rest/api/2/issueLinkType

Creates an issue link type. Use this operation to create descriptions of the reasons why issues are linked. The issue link type consists of a name and descriptions for a link's inward and outward relationships.

To use this operation, the site must have issue linking enabled.

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
id String No

The ID of the issue link type and is used as follows:

  • In the issueLink resource it is the type of issue link. Required on create when name isn't provided. Otherwise, read only.
  • In the issueLinkType resource it is read only.
name String No

The name of the issue link type and is used as follows:

  • In the issueLink resource it is the type of issue link. Required on create when id isn't provided. Otherwise, read only.
  • In the issueLinkType resource it is required on create and optional on update. Otherwise, read only.
inward String No

The description of the issue link type inward link and is used as follows:

  • In the issueLink resource it is read only.
  • In the issueLinkType resource it is required on create and optional on update. Otherwise, read only.
self String No

The URL of the issue link type. Read only.

outward String No

The description of the issue link type outward link and is used as follows:

  • In the issueLink resource it is read only.
  • In the issueLinkType resource it is required on create and optional on update. Otherwise, read only.

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.