POST /rest/api/2/issue/{issueIdOrKey}/worklog/move
Moves a list of worklogs from one issue to another. This is an experimental API with several limitations:
- You can't move more than 5000 worklogs at once.
- You can't move worklogs containing an attachment.
- You can't move worklogs restricted by project roles.
- No notifications will be sent for moved worklogs.
- No webhooks or events will be sent for moved worklogs.
- No issue history will be recorded for moved worklogs.
Time tracking must be enabled in Jira, otherwise this operation returns an error. For more information, see Configuring time tracking.
Permissions required:
- Browse projects project permission for the projects containing the source and destination issues.
- If issue-level security is configured, issue-level security permission to view the issue.
- Delete all worklogsand Edit all worklogsproject permission
- If the worklog has visibility restrictions, belongs to the group or has the role visibility is restricted to.
Servers
- https://your-domain.atlassian.net
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
issueIdOrKey |
String | Yes |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
overrideEditableFlag |
Boolean | No |
Whether the work log entry should be moved to and from the issues even if the issues are not editable, because jira.issue.editable set to false or missing. For example, the issue is closed. Connect and Forge app users with admin permission can use this flag. Default value: false |
adjustEstimate |
String | No |
Defines how to update the issues' time estimate, the options are:
Possible values:
Default value: "auto" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
issueIdOrKey |
String | No |
The issue id or key of the destination issue |
ids[] |
Array | No |
A list of worklog IDs. |
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.