Jira
The Jira node lets you interact with Jira Cloud for issue tracking and project management. A single node supports all operations — select the operation you need and the relevant fields appear.
All operations require a Jira connection configured with your domain, email, and API token.
Operations
Issues: Search (JQL)
Search for issues using Jira Query Language (JQL).
| Field | Description | Notes |
|---|---|---|
| JQL Query | JQL expression to search for issues | Required. Supports templates |
| Max Results | Maximum number of issues to return | Default: 50, max: 1000 |
JQL Examples:
project = PROJ AND status = "In Progress"
assignee = currentUser() AND updated >= -7d
labels IN ("bug", "critical") ORDER BY priority DESCReturns an array of Jira issue objects with key, fields, id, etc.
Issues: Get
Retrieve a single issue by key.
| Field | Description | Notes |
|---|---|---|
| Issue Key | The issue key (e.g., PROJ-123) | Required. Supports templates |
Issues: Create
Create a new issue.
| Field | Description | Notes |
|---|---|---|
| Project Key | Project to create the issue in (e.g., PROJ) | Required. Supports templates |
| Issue Type | Type name: Task, Bug, Story, etc. | Optional — uses project default |
| Summary | Issue title | Required. Supports templates |
| Description | Issue description (plain text) | Optional. Auto-converted to Atlassian Document Format |
| Additional Fields | Key-value pairs for extra fields (priority, labels, assignee, etc.) | Optional. Supports templates |
Issues: Update
Update an existing issue's fields.
| Field | Description | Notes |
|---|---|---|
| Issue Key | The issue to update | Required. Supports templates |
| Description | Updated description | Optional |
| Additional Fields | Fields to update as key-value pairs | Optional |
Issues: Transition
Move an issue to a new status (e.g., "To Do" to "In Progress").
| Field | Description | Notes |
|---|---|---|
| Issue Key | The issue to transition | Required. Supports templates |
| Transition ID | Numeric transition ID | Required. Supports templates |
TIP
To find available transition IDs, use Issues: Get on an issue — the response includes available transitions. You can also find them in your Jira project's workflow configuration.
Issues: Add Comment
Add a comment to an issue.
| Field | Description | Notes |
|---|---|---|
| Issue Key | The issue to comment on | Required. Supports templates |
| Description | Comment body (plain text) | Required. Auto-converted to Atlassian Document Format |
Issues: Delete
Delete an issue.
| Field | Description | Notes |
|---|---|---|
| Issue Key | The issue to delete | Required. Supports templates |
Projects: List
List all projects accessible to the authenticated user. No additional configuration needed.
Projects: Get
Get details for a specific project.
| Field | Description | Notes |
|---|---|---|
| Project Key | Project key (e.g., PROJ) | Required. Supports templates |
Users: Search
Search for Jira users.
| Field | Description | Notes |
|---|---|---|
| Max Results | Maximum users to return | Default: 50 |
Streaming
Search operations (Issues: Search, Projects: List, Users: Search) support streaming — each result is emitted individually to downstream nodes. Mutation operations process each upstream item sequentially.
Common Patterns
Search and Update
- Jira (Issues: Search) — find issues matching criteria
- Transform — compute new values
- Jira (Issues: Update) — apply changes to each issue
Create Issues from Data
- Google Sheets Read or DataStore Query — fetch source data
- Transform — map fields to Jira format
- Jira (Issues: Create) — create an issue per row