Bulk moving issues to a different queue

Use this request to move multiple issues to another queue at the same time.

POST

https://api.tracker.yandex.net/v3/bulkchange/_move

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.

If an issue you want to move has a type and status that are missing in the target queue, no transfer will be made. To reset the issue status to the initial value when moving it, use the InitialStatus parameter.

By default, when an issue is moved, the values of its components, versions, and projects are cleared. If the new queue has the same values of the fields specified, use the MoveAllFields parameter to move the components, versions, and projects.

Query format

Before making a request, get permission to access the API.

To move issues to another queue, use an HTTP POST request:

POST /v3/bulkchange/_move
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth_token>
X-Org-ID or X-Cloud-Org-ID: <organization_ID>

{
  "queue": "<queue_key>",
  "issues": ["TEST-1","TEST-2","TEST-3"]
}
Headers
  • Host: Address of the node that provides the API.

  • Authorization: Authorization token about these formats:

    • OAuth <OAuth_token>: For authorization using the OAuth 2.0 protocol. Learn more

    • Bearer <IAM_token>: For authorization using an IAM token, if a Yandex Cloud Organization organization is linked to Tracker. Learn more

  • 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 Cloud Organization.

    To get the organization ID, go to AdministrationOrganizations and copy the value from the ID field.

Request parameters

Additional parameters

Parameter Description Data type
notify Flag indicating if users should be notified about issue changes:
  • true: Users specified in the issue fields are notified.
  • false (by default): No users are notified.
Boolean
Request body parameters

Required parameters

Parameter Description Data type
queue Queue key to move the issues to. String
issues IDs of the issues to be moved. String

Additional parameters

Parameter Description Data type
values Issue parameters that will be updated during the move. Use the parameters that are available when editing the issue. String
moveAllFields Shows whether to move the issue's versions, components, and projects to the new queue:
  • true: Move them if the new queue has similar versions, components, and projects.
  • false (by default): Clear the versions, components, and projects.
Boolean
initialStatus Resetting the issue status. Reset the status when moving an issue to a queue with a different workflow:
  • true: Reset the status.
  • false (by default): Retain the current status.
Boolean

Request example: Move issues.

  • An HTTP POST method is used.
  • The TEST-1, TEST-2, and TEST-3 issues are moved to the CHECK queue.
  • Each moved issue is assigned the moved tag.
POST /v3/bulkchange/_move
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth_token>
X-Org-ID or X-Cloud-Org-ID: <organization_ID>

{
"queue": "CHECK",
"issues": ["TEST-1","TEST-2","TEST-3"],
"values": {
   "tags": {
   "add": ["moved"]
   }
},
"moveAllFields": true
}

Response format

If the request is successful, the API returns a response with code 201 Created.

The response body contains information about the bulk move operation in JSON format.

{
    "id": "1ab23cd4e5678901********",
    "self": "https://api.tracker.yandex.net/v3/bulkchange/1ab23cd4e5678901********",
    "createdBy": {
        "self": "https://api.tracker.yandex.net/v3/users/12********",
        "id": "12********",
        "display": "Full name"
    },
    "createdAt": "2020-12-15T11:52:53.665+0000",
    "status": "CREATED",
    "statusText": "Bulk change task created.",
    "executionChunkPercent": 0,
    "executionIssuePercent": 0
}
Response parameters
Parameter Description Data type
id Bulk change operation ID. String
self Address of the API resource with information about the bulk change. String
createdBy Object with information about the user who made the bulk change. Map item
createdAt Date and time when the bulk change operation was created. String
status Bulk change operation status. String
statusText Description of the bulk change operation status. String
executionChunkPercent Service parameter Number
executionIssuePercent Service parameter Number

createdBy object fields

Parameter Description Data type
self Address of the API resource with information about the user String
id User ID. Number
display Displayed user name String

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

400
One or more request parameters have an invalid value.
401
The user is not authorized. Make sure that actions described in the API access section are performed.
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.
422
JSON validation error, the request is rejected.