POST /rest/api/2/version/{id}/removeAndSwap
Deletes a project version.
Alternative versions can be provided to update issues that use the deleted version in fixVersion, affectedVersion, or any version picker custom fields. If alternatives are not provided, occurrences of fixVersion, affectedVersion, and any version picker custom field, that contain the deleted version, are cleared. Any replacement version must be in the same project as the version being deleted and cannot be the version being deleted.
This operation can be accessed anonymously.
Permissions required: Administer Jira global permission or Administer Projects project permission for the project that contains the version.
Servers
- https://your-domain.atlassian.net
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The ID of the version. |
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 |
|---|---|---|---|
moveFixIssuesTo |
Integer | No |
The ID of the version to update |
customFieldReplacementList[] |
Array | No |
An array of custom field IDs ( |
customFieldReplacementList[].moveTo |
Integer | No |
The version number to use as a replacement for the deleted version. |
customFieldReplacementList[].customFieldId |
Integer | No |
The ID of the custom field in which to replace the version number. |
moveAffectedIssuesTo |
Integer | No |
The ID of the version to update |
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.