Create Issue
taiga.create_issue
ActionBusiness appsconnection required
Calls the Taiga API with the connection's credentials.
Create an issue in a project.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Taiga
- Secret shape
- the Taiga auth token as {"auth_token": "…"}, or {"username": "…", "password": "…"} to log in with
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
13 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project Id of the Taiga project. This is the numeric primary key, not the project slug. | integer | Yes | — | ≥ 1 | 1 |
subject The issue's one-line subject, shown everywhere Taiga lists it. | string | Yes | — | — | Checkout returns a 500 on retry |
description The issue body, written as Markdown. Leave blank to keep Taiga's default. | string | No | — | — | — |
assigned_to Id of the user the issue is assigned to. | integer | No | — | ≥ 1 | — |
status Id of the issue status to set, from the project's issue statuses. | integer | No | — | ≥ 1 | — |
severity Id of the severity to set, from the project's severities. | integer | No | — | ≥ 1 | — |
priority Id of the priority to set, from the project's priorities. | integer | No | — | ≥ 1 | — |
type Id of the issue type to set, from the project's issue types. | integer | No | — | ≥ 1 | — |
milestone Id of the sprint (milestone) to attach the issue to. | integer | No | — | ≥ 1 | — |
tags Tags to set on the issue. A comma-separated string is accepted too. | array | No | — | array of string | ["backend","regression"] |
is_blocked Whether to mark the issue as blocked. | boolean | No | — | — | — |
blocked_note The reason the issue is blocked, shown next to the blocked flag. | string | No | — | — | — |
is_closed Whether the issue should be treated as closed. | boolean | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"project": 1,
"subject": "Checkout returns a 500 on retry",
"tags": [
"backend",
"regression"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Taiga's internal primary key for the issue. | number | — |
ref The per-project reference number shown in the Taiga UI. | number | — |
subject The issue's one-line subject. | string | — |
description The issue body, as Markdown. | string | — |
description_html The issue body rendered to HTML by Taiga. | string | — |
project Id of the project the issue belongs to. | number | — |
project_extra_info The project's id, name, slug and logo URL. | object | — |
status Id of the issue status. | number | — |
status_extra_info The status name, colour and whether it closes. | object | — |
severity Id of the issue severity. | number | — |
priority Id of the issue priority. | number | — |
type Id of the issue type. | number | — |
milestone Id of the sprint the issue is assigned to, if any. | number | — |
owner Id of the user who created the issue. | number | — |
owner_extra_info The creator's id, username and display name. | object | — |
assigned_to Id of the assignee, or null when unassigned. | number | — |
assigned_to_extra_info The assignee's id, username and display name. | object | — |
is_blocked Whether the issue is currently marked blocked. | boolean | — |
blocked_note The reason the issue is blocked. | string | — |
is_closed Whether the issue's status is a closing one. | boolean | — |
tags The issue's tags, each a [name, colour] pair. | array | — |
watchers Ids of the users watching the issue. | array | — |
total_watchers How many users watch the issue. | number | — |
total_voters How many users have voted for the issue. | number | — |
due_date The due date as an ISO-8601 date, or null when unset. | string | — |
created_date When the issue was created, as an ISO-8601 timestamp. | string | — |
modified_date When the issue last changed, as an ISO-8601 timestamp. | string | — |
finished_date When the issue was closed, as an ISO-8601 timestamp. | string | — |
version The concurrency version to send back on the next update. | number | — |
{
"assigned_to": 0,
"assigned_to_extra_info": {},
"blocked_note": "",
"created_date": "",
"description": "",
"description_html": "",
"due_date": "",
"finished_date": "",
"id": 0,
"is_blocked": false,
"is_closed": false,
"milestone": 0,
"modified_date": "",
"owner": 0,
"owner_extra_info": {},
"priority": 0,
"project": 0,
"project_extra_info": {},
"ref": 0,
"severity": 0,
"status": 0,
"status_extra_info": {},
"subject": "",
"tags": [],
"total_voters": 0,
"total_watchers": 0,
"type": 0,
"version": 0,
"watchers": []
}See Create Issue run in a workflow.
In a technical demo we add the Taiga connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.