Issue worklogs
Bulk move worklogs
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 worklogs project permission
- Work on issues project permission to log work on an issue, that is to create a worklog entry, if time tracking is enabled. This permission is required as a prerequisite for applying the other time-tracking permissions
- If the worklog has visibility restrictions, belongs to the group or has the role visibility is restricted to.
post/rest/api/3/issue/{issueIdOrKey}/worklog/move
Path parameters
issueIdOrKeystring required
Query parameters
adjustEstimate'leave' | 'auto'
Defines how to update the issues' time estimate, the options are:
- leave Leaves the estimate unchanged.
- auto Reduces the estimate by the aggregate value of timeSpent across all worklogs being moved in the source issue, and increases it in the destination issue.
overrideEditableFlagboolean
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.
Request body
Response
Returned if the request is partially successful.