Creating an issue type
Use this request to create a new issue type.
POST
https://api.tracker.yandex.net/v3/issuetypes/
You need Administrator rights to run this request.
Query format
Before making a request, get permission to access the API.
To create an issue type, make an HTTP POST
request. In the request body, specify the parameters in JSON format:
POST /v3/issuetypes/
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth token>
X-Org-ID or X-Cloud-Org-ID: <organization_ID>
{
"key": "client",
"name": {
"ru": "Клиент",
"en": "Customer"
}
}
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
orX-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 Administration → Organizations and copy the value from the ID field.
-
Request body parameters
The request body contains the information needed to create a new issue type:
Required parameters
Parameter | Description | Data type |
---|---|---|
key | Key of the issue type | String |
name | Issue type name | Map object |
Fields of the name
object
Parameter | Description | Data type |
---|---|---|
ru | Issue type name in Russian | String |
en | Issue type name in English | String |
Response format
If the request is successful, the API returns a response with code 201 Created
.
The response body contains information about the created issue type in JSON format.
[
{
"self": "https://api.tracker.yandex.net/v3/issuetypes/23",
"id": 23,
"version": 1,
"key": "client",
"name": "Customer"
}
]
Response parameters
Parameter | Description | Data type |
---|---|---|
self | Address of the API resource with information about the issue type | String |
id | Unique ID of the issue type in Yandex Tracker | Number |
version | Version of the issue type | Number |
key | Key of the issue type | String |
name | Issue type name | String |
- 404
- The requested object was not found. You may have specified an invalid object ID or key.
- 409
- There was a conflict when editing the object. The error may be due to an invalid update version.