---
metadata:
  - name: generator
    content: Diplodoc Platform v5.66.1
  - property: og:type
    content: article
  - property: article:section
    content: API reference
  - property: og:title
    content: Move an issue to another queue using an API request
  - property: article:tag
    content: Technical instructions
alternate:
  - https://yandex.ru/support/tracker/en/api/issues/move-issue.md
  - https://yandex.ru/support/tracker/ru/api/issues/move-issue.md
  - href: https://yandex.ru/support/tracker/en/api/issues/move-issue.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.ru/support/tracker/en/llms.txt?revision=r22057024
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt?revision=r22057024


# Move an issue to another queue using an API request

Use this request to move an issue to a different queue.

<div class="request_example yfm-code-floating-container method_post">
    <p>POST</p>
    <pre><code>https://api.tracker.yandex.net/v3/issues/{issue_ID}/_move?queue=QUEUE_KEY</code></pre>
    <button class="yfm-clipboard-button"><svg width="16" height="16" viewBox="0 0 24 24" class="yfm-clipboard-icon" data-animation="15">
    <path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path>
    <path stroke="currentColor" fill="transparent" strokewidth="1.5" d="M9.5 13l3 3l5 -5" visibility="hidden">
        <animate id="visibileAnimation-15" attributeName="visibility" from="hidden" to="visible" dur="0.2s" fill="freeze" begin=""></animate>
        <animate id="hideAnimation-15" attributeName="visibility" from="visible" to="hidden" dur="1s" begin="visibileAnimation-15.end+1" fill="freeze"></animate>
    </path>
</svg>
</button>
</div>

<!-- source: en/api/_assets/style/methods.md -->

<!-- endsource: en/api/_assets/style/methods.md -->

Before executing the request, make sure the user has permission to edit the issues to be moved and is allowed to create them in the new queue.

Consider the behavior specifics when moving an issue:

#|
|| **Situation** | **Limit** ||
|| **Different workflows**
|
If the issue type has different [workflows](*workflow) configured in the source and target queues, only the organization administrator can move the issue while keeping its current status.

Other users are not allowed to perform such a move. ||
|| **Type and status**
|
If the type or status of the issue being moved does not exist in the new queue, the move will not be performed.

To reset the status to its initial value, use the `initialStatus=true` parameter. ||
|| **Components, versions, and projects**
|
By default, they are cleared when moving.

If the new queue has similar values configured, use the `moveAllFields=true` parameter. ||
|| **Local fields**
|
Values of [local fields](https://yandex.com/support/tracker/local-fields.html) will be deleted when moving to another queue. ||
|#

## Query format {#query}

Before making a request, [get permission to access the API](https://yandex.ru/support/tracker/en/api/access.md).

To move issues, use an HTTP `POST` request:

```json translate=no
POST /v3/issues/{id_задачи}/_move?queue=QUEUE_KEY
Host: api.tracker.yandex.net
Authorization: OAuth API_TOKEN
X-Org-ID or X-Cloud-Org-ID: ORGANIZATION_ID
```
<!-- source: en/api/_includes/headings-no-body.md -->
{% cut "Headers" %}

* `Host`: address of the node that provides the API.

* <!-- source: en/api/_includes/authorization.md -->
  `Authorization`: Authorization token about these formats:

    - `OAuth OAUTH_TOKEN`: For authorization using the OAuth 2.0 protocol. [Learn more](https://yandex.ru/support/tracker/en/api/access.md#about_OAuth)

    - `Bearer IAM_TOKEN`: For authorization using an IAM token, if a Yandex Identity Hub organization is linked to Tracker. [Learn more](https://yandex.ru/support/tracker/en/api/access.md#iam-token)
  <!-- endsource: en/api/_includes/authorization.md -->


* <!-- source: en/api/_includes/org-id.md -->
  # ID types {#types}


  `X-Org-ID` or `X-Cloud-Org-ID`: Organization ID.

  - Use the `X-Org-ID` header if a Tracker organization is linked to Yandex 360 for Business.

  - Use the `X-Cloud-Org-ID` header if a Tracker organization is linked to Yandex Identity Hub.


  # Finding the ID {#find-id}


  To get the organization ID, go to **Administration** → [**Organizations**](https://tracker.yandex.com/admin/orgs) and copy the value from the **ID** field.
  <!-- endsource: en/api/_includes/org-id.md -->


{% endcut %}
<!-- endsource: en/api/_includes/headings-no-body.md -->

<!-- source: en/api/_includes/resource-issue-id.md -->
{% cut "Resource" %}

| Parameter | Description | Data type |
-------- | -------- | ----------
| `issue_key_or_ID` | ID or key of the current issue. | String |

{% endcut %}
<!-- endsource: en/api/_includes/resource-issue-id.md -->

{% cut "Request parameters" %}

**Required parameters**

Parameter | Description | Data type
----- | ----- | -----
queue | Key of the queue to which the issue should be moved. | String

**Additional parameters**

Parameter | Description | Data type
----- | ----- | -----
notify | Flag indicating whether to notify about the issue change:<ul><li>`true` – (default) users specified in the issue fields will receive notifications;</li><li>`false` – users will not receive notifications.</li></ul> | Boolean
notifyAuthor | Flag indicating whether to notify the issue author:<ul><li>`true` – the author will receive a notification;</li><li>`false` (default) – the author will not receive a notification.</li></ul> | Boolean
moveAllFields | Moving the issue's versions, components, and projects to the new queue:<ul><li>`true` – move them if the corresponding versions, components, and projects exist in the new queue;</li><li>`false` (default) – clear the versions, components, and projects.</li></ul> | Boolean
initialStatus | Resetting the issue status to its initial value. The status must be reset if the issue is moved to a queue with a different [workflow](*workflow):<ul><li>`true` – the status will be reset;</li><li>`false` (default) – the status will remain unchanged.</li></ul> | Boolean
expand | Additional fields to be included in the response:<ul><li>`attachments` – attachments;</li><li>`comments` – comments;</li><li>`workflow` – issue workflow;</li><li>`transitions` – lifecycle transitions.</li></ul> | String

{% endcut %}

{% cut "Request body parameters" %}

You can use the request body if you need to change the parameters of the issue being moved. The request body has the same format as when [editing issues](https://yandex.ru/support/tracker/en/api/issues/patch-issue.md#req-body-params).

{% endcut %}

> Example: Moving an issue
>
> - An HTTP POST method is used.
> - Moving the **TEST-1** issue to the **NEW** queue.
>
> ```
> POST https://api.tracker.yandex.net/v3/issues/TEST-1/_move?queue=NEW
> ```

## Response format {#answer}

{% list tabs %}

- Request executed successfully

    <!-- source: en/api/_includes/answer-200.md -->
    If the request is successful, the API returns a response with code `200 OK`.
    <!-- endsource: en/api/_includes/answer-200.md -->

    The response body contains the results in JSON format.

    ```json translate=no
    {
        "self": "https://api.tracker.yandex.net/v3/issues/NEW-1",
        "id": "1a********",
        "key": "NEW-1",
        "version": 2,
        "aliases": [
            "TEST-1"
        ],
        "previousQueue": {
            "self": "https://api.tracker.yandex.net/v3/queues/TEST",
            "id": "3",
            "key": "TEST",
            "display": "TEST"
        },
        "description": "My description",
        "type": {
            "self": "https://api.tracker.yandex.net/v3/issuetypes/2",
            "id": "2",
            "key": "task",
            "display": "Task"
        },
        "createdAt": "2020-09-04T14:18:56.776+0000",
        "updatedAt": "2020-11-12T12:38:19.040+0000",
        "lastCommentUpdatedAt": "2020-10-18T13:33:44.291+0000",
        "summary": "Тест",
        "updatedBy": {
            "self": "https://api.tracker.yandex.net/v3/users/11********",
            "id": "11********",
            "display": "User Name"
        },
        "priority": {
            "self": "https://api.tracker.yandex.net/v3/priorities/3",
            "id": "3",
            "key": "normal",
            "display": "Normal"
        },
        "followers": [
            {
                "self": "https://api.tracker.yandex.net/v3/users/11********",
                "id": "11********",
                "display": "User Name"
            }
        ],
        "createdBy": {
            "self": "https://api.tracker.yandex.net/v3/users/11********",
            "id": "11********",
            "display": "User Name"
        },
        "assignee": {
            "self": "https://api.tracker.yandex.net/v3/users/11********",
            "id": "11********",
            "display": "User Name"
        },
        "queue": {
            "self": "https://api.tracker.yandex.net/v3/queues/NEW",
            "id": "5",
            "key": "NEW",
            "display": "My queue"
        },
        "status": {
            "self": "https://api.tracker.yandex.net/v3/statuses/1",
            "id": "1",
            "key": "open",
            "display": "Open"
        },
        "previousStatus": {
            "self": "https://api.tracker.yandex.net/v3/statuses/3",
            "id": "3",
            "key": "resolved",
            "display": "Resolved"
        },
        "favorite": false
    }
    ```

    {% cut "Response parameters" %}

    <!-- source: en/api/_includes/issue-response-fields-note.md -->
    {% note info "" %}

    The table lists the main response fields. For a full list of fields and their descriptions, see [Response parameters](https://yandex.ru/support/tracker/en/api/issues/response-fields.md).

    The response may also include global user fields and local queue fields.

    {% endnote %}
    <!-- endsource: en/api/_includes/issue-response-fields-note.md -->

    Parameter | Description | Data type
    ----- | ----- | -----
    self | API resource address that contains information about the issue. | String
    id | Issue ID. | String
    key | Issue key. | String
    version | Issue version. Each change of issue parameters increments the version number. <br>Issue editing will be blocked if the version reaches the limit: for robots `10100`, for users `11100`. | Number
    aliases | Array with information about the issue's alternative keys. | Array of strings
    [previousQueue](#previous-queue) | Object with information about the issue's previous queue. | Object
    description | Issue description. | String
    [type](#type) | Object with information about the issue type. | Object
    createdAt | Issue creation date and time. | String
    updatedAt | Date and time of the issue update. | String
    lastCommentUpdatedAt | Date and time of the last added comment. | String
    summary | Issue summary. | String
    [updatedBy](#updated-by) | Object with information about the last user who changed the issue. | Object
    [priority](#priority) | Object with information about the priority. | Object
    [followers](#followers) | Array of objects with information about the issue followers. | Array of strings
    [createdBy](#created-by) | Object with information about the issue reporter. | Object
    [assignee](#assignee) | Object with information about the issue assignee. | Object
    [queue](#queue) | Object with information about the issue queue. | Object
    [status](#status) | Object with information about the issue status. | Object
    [previousStatus](#previousStatus) | Object with information about the previous issue status. | Object
    favorite | Flag indicating a favorite issue:<ul><li>`true` – notifications are disabled;</li><li>`false` – notifications are enabled.</li></ul> | Boolean

    `previousQueue` **object fields** {#previous-queue}

    <!-- source: en/api/_includes/queue.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the queue. | String |
    | id | Queue ID. | String |
    | key | Queue key. | String |
    | display | Queue name displayed. | String |
    <!-- endsource: en/api/_includes/queue.md -->

    <!-- source: en/api/_includes/type.md -->
    `type` **object fields** {#type}

    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the issue type. | String |
    | id | Issue type ID | String |
    | key | Issue type key. | String |
    | display | Issue type name displayed. | String |
    <!-- endsource: en/api/_includes/type.md -->

    `updatedBy` **object fields** {#updated-by}

    <!-- source: en/api/_includes/user.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the user | String |
    | id | User ID. | String |
    | display | Displayed user name | String |
    | passportUid | Unique ID of the user account in the Yandex 360 for Business organization and Yandex ID. | Number |
    | cloudUid | Unique user ID in Yandex Identity Hub | String |
    <!-- endsource: en/api/_includes/user.md -->

    <!-- source: en/api/_includes/priority.md -->
    `priority` **object fields** {#priority}

    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the priority. | String |
    | id | Priority ID | String |
    | key | Priority key. | String |
    | display | Priority name displayed. | String |
    <!-- endsource: en/api/_includes/priority.md -->

    `followers` **array object fields** {#followers}

    <!-- source: en/api/_includes/user.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the user | String |
    | id | User ID. | String |
    | display | Displayed user name | String |
    | passportUid | Unique ID of the user account in the Yandex 360 for Business organization and Yandex ID. | Number |
    | cloudUid | Unique user ID in Yandex Identity Hub | String |
    <!-- endsource: en/api/_includes/user.md -->

    `createdBy` **object fields** {#created-by}

    <!-- source: en/api/_includes/user.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the user | String |
    | id | User ID. | String |
    | display | Displayed user name | String |
    | passportUid | Unique ID of the user account in the Yandex 360 for Business organization and Yandex ID. | Number |
    | cloudUid | Unique user ID in Yandex Identity Hub | String |
    <!-- endsource: en/api/_includes/user.md -->

    `assignee` **object fields** {#assignee}

    <!-- source: en/api/_includes/user.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the user | String |
    | id | User ID. | String |
    | display | Displayed user name | String |
    | passportUid | Unique ID of the user account in the Yandex 360 for Business organization and Yandex ID. | Number |
    | cloudUid | Unique user ID in Yandex Identity Hub | String |
    <!-- endsource: en/api/_includes/user.md -->

    `queue` **object fields** {#queue}

    <!-- source: en/api/_includes/queue.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the queue. | String |
    | id | Queue ID. | String |
    | key | Queue key. | String |
    | display | Queue name displayed. | String |
    <!-- endsource: en/api/_includes/queue.md -->

    `status` **object fields** {#status}

    <!-- source: en/api/_includes/status.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the status. | String |
    | id | Status ID. | String |
    | key | Status key. | String |
    | display | Status name displayed. | String |
    <!-- endsource: en/api/_includes/status.md -->

    `previousStatus` **object fields** {#previousStatus}

    <!-- source: en/api/_includes/status.md -->
    | Parameter | Description | Data type |
    ----- | ----- | -----
    | self | Address of the API resource with information about the status. | String |
    | id | Status ID. | String |
    | key | Status key. | String |
    | display | Status name displayed. | String |
    <!-- endsource: en/api/_includes/status.md -->

    {% endcut %}

- Request failed

    If the request is processed incorrectly, the API returns a response with an error code:

    <!-- source: en/api/_includes/answer-error-401.md -->
    401
    :   The user is not authorized. Make sure that actions described in the [API access](https://yandex.ru/support/tracker/en/api/access.md) section are performed.
    <!-- endsource: en/api/_includes/answer-error-401.md -->

    <!-- source: en/api/_includes/answer-error-403.md -->
    403
    :   You are not authorized to perform this action. You can check what rights you have in the Tracker interface. The same rights are required to perform an action via the API and interface.
    <!-- endsource: en/api/_includes/answer-error-403.md -->

    <!-- source: en/api/_includes/answer-error-404.md -->
    404
    :   The requested object was not found. You may have specified an invalid object ID or key.
    <!-- endsource: en/api/_includes/answer-error-404.md -->

    <!-- source: en/api/_includes/answer-error-423.md -->
    423
    :   Object edits disabled. The `version` parameter value limit (the maximum number of object updates) might have been exceeded. The maximum version value is `10100` for robots and `11100` for users.
    <!-- endsource: en/api/_includes/answer-error-423.md -->

{% endlist %}

[*workflow]: A workflow is a set of issue statuses and rules for transitioning between them. You can set up multiple workflows in each queue.