PUT /rest/api/2/issuetypescheme/{issueTypeSchemeId}/issuetype/move
Changes the order of issue types in an issue type scheme.
The request body parameters must meet the following requirements:
- all of the issue types must belong to the issue type scheme.
- either
afterorpositionmust be provided. - the issue type in
aftermust not be in the issue type list.
Permissions required: Administer Jira global permission.
Servers
- https://your-domain.atlassian.net
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
issueTypeSchemeId |
Integer | Yes |
The ID of the issue type scheme. |
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 |
|---|---|---|---|
after |
String | No |
The ID of the issue type to place the moved issue types after. Required if |
issueTypeIds[] |
Array | Yes |
A list of the issue type IDs to move. The order of the issue type IDs in the list is the order they are given after the move. |
position |
String | No |
The position the issue types should be moved to. Required if Possible values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.