Assign Issue
jira.assign_issue
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Set or clear the assignee on a Jira issue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 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 |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
account_id The assignee's Atlassian accountId. Use '-1' for the project's default assignee, or leave blank to unassign the issue. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
key The issue key the call acted on. | string | PROJ-123 |
account_id The accountId assigned, or null when unassigned. | string | — |
{
"account_id": "",
"key": "PROJ-123",
"ok": false
}Notes
- Find an accountId with jira.search_users or jira.list_assignable_users.
See Assign Issue run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.