---
title: "Bulk move worklogs"
method: POST
path: "/rest/api/3/issue/{issueIdOrKey}/worklog/move"
tags: ["Issue worklogs"]
---

# Bulk move worklogs

`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.

## Path parameters

- `issueIdOrKey` string, required

## Query parameters

- `adjustEstimate` 'leave' | 'auto'
- `overrideEditableFlag` boolean

## Request body

- WorklogsMoveRequestBean
  - `ids` integer[] — A list of worklog IDs.
  - `issueIdOrKey` string — The issue id or key of the destination issue

## Response `200`

Returned if the request is partially successful.

## Other responses

- `204` — Returned if the request is successful.
- `400` — Returned if: * `request` is not provided or is invalid * the user does not have permission to move the worklogs * the number of worklogs being moved exceeds the limit * the total size of worklogs being moved is too large * any worklog contains attachments
- `401` — Returned if the authentication credentials are incorrect.
- `404` — Returned if: * the source or destination issue is not found or the user does not have permission to view the issues * at least one of the worklogs is not associated with the provided issue * time tracking is disabled

---

[API](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-3.md) · [All operations](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/the-jira-cloud-platform-rest-api-3/versions/5a51740d7ab3/schema)