provider Issue worklogs POST /rest/api/3/issue/{issueIdOrKey}/worklog/move
@utdk/jira /rest/api/3/issue/{issueIdOrKey}/worklog/move
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](https://confluence.atlassian.com/x/qoXKM). **[Permissions](#permissions) required:** * *Browse projects* [project permission](https://confluence.atlassian.com/x/yodKLg) for the projects containing the source and destination issues. * If [issue-level security](https://confluence.atlassian.com/x/J4lKLg) is configured, issue-level security permission to view the issue. * *Delete all worklogs* [project permission](https://confluence.atlassian.com/x/yodKLg) * *Work on issues* [project permission](https://confluence.atlassian.com/x/yodKLg) 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.
issueIdOrKey path required
string
adjustEstimate query
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.
enum: leave, auto
overrideEditableFlag query
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.
boolean

Try it

Authentication
Configure credentials for The Jira Cloud platform REST API
Gateway
The gateway proxies requests and injects credentials server-side. Configure credentials above, then enter your gateway URL.

Saved automatically to browser storage.

bulkmoveworklogs
POST/rest/api/3/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](https://confluence.atlassian.com/x/qoXKM). **[Permissions](#permissions) required:** * *Browse projects* [project permission](https://confluence.atlassian.com/x/yodKLg) for the projects containing the source and destination issues. * If [issue-level security](https://confluence.atlassian.com/x/J4lKLg) is configured, issue-level security permission to view the issue. * *Delete all worklogs* [project permission](https://confluence.atlassian.com/x/yodKLg) * *Work on issues* [project permission](https://confluence.atlassian.com/x/yodKLg) 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.

Parameters

required

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.

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.

Input

A list of worklog IDs.

The issue id or key of the destination issue

Enter a gateway URL above to enable sending.

Code snippet
Updates live as you fill in the form above.

TypeScript

import jira from '@utdk/jira';

await jira.bulkmoveworklogs({
  "adjustEstimate": "auto",
  "overrideEditableFlag": false
})