Jira action
Runs one operation against Jira. In the action picker it is Jira, under Integration Actions. One action, 12 operations: pick the connection, choose the operation, and the form asks for what that operation needs.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | Yes | The Jira connection to use. |
| Operation | Yes | What to do. Choosing one reveals its own inputs. |
There is no project field on the action itself. The two operations that need one—Create Issue and Search Issues—carry their own, because everything else addresses an issue by key and the key already says which project it is in. Picking the project also scopes the pickers below it, so an issue type or a custom field is chosen from what that project actually offers.
Most text inputs accept variables, so an operation can work on the trigger's data and earlier results.
Operations
| Operation | What it takes |
|---|---|
| Create Issue | A project, an issue type from that project, a summary, and optionally a description, an assignee, a priority, labels, and custom fields. |
| Get Issue | An issue key. |
| Update Issue | An issue key, plus the summary, description, assignee, priority, labels, or custom fields to change. |
| Assign Issue | An issue key and an assignee. Leave the assignee blank to unassign. |
| Transition Issue | An issue key and the transition to apply. |
| Add Comment | An issue key and the comment body. |
| Search Issues | A JQL query, optionally scoped to a project, with a result cap and a choice of which fields to return. |
| Delete Issue | An issue key, and whether to delete its subtasks with it. |
| Add Worklog | An issue key, the time spent, and optionally a comment and a start time. |
| Link Issues | Two issue keys, the link type, and an optional comment. |
| Add Watcher | An issue key and the account to add. |
| Remove Watcher | An issue key and the account to remove. |
Writing a description or a comment
Anywhere Jira takes rich text—an issue description, a comment body—the field is a choice of two:
| Type | Use it when |
|---|---|
| Formatted | You are writing the text here. A toolbar handles the formatting, and what you write is converted to Jira's own markup on the way out. |
| Raw Wiki Markup | The text arrives from a variable that already holds Jira wiki syntax. It is passed through as written. |
Searching
Search Issues returns at most 50 issues when you leave the cap blank, and Jira caps it at 1000. Setting a project both scopes the field picker and narrows the query to that project, so the JQL is optional once a project is chosen—without either, there is nothing to search.
Beyond the core details every result carries—key, summary, status, and type—you choose which fields come back, so a later step reads what it needs without the rest.
Output
The result of the operation: for most, the affected issue or comment; for Search Issues, the matched issues with their paging information.