Jira Action
Creates, finds and moves Jira issues from a flow. Twelve operations over Atlassian Cloud, including JQL search and issue transitions — the two that turn a webhook into “file it, assign it, move it to In Progress”.
Setup
An Atlassian connection. The scopes it was granted decide what the node can do: reading issues and writing them are separate permissions, so a read-only connection fails on create with a 403.
Mode — action or AI toolkit
The Mode selector decides who drives the node. In Action mode you pick one operation and fill its fields, and the node does that every time it runs. In AI toolkit mode the operations become tools an AI Node can call, and the model chooses which one and with what arguments.
Operations
The Operation dropdown decides what the node does and which fields appear under it. These are the exact values the API validates against:
| Value | In the dropdown | What it does |
|---|---|---|
| createIssue | Create issue | Creates an issue in a project. |
| getIssue | Get issue | Reads one issue by its key. |
| updateIssue | Update issue | Changes fields on an issue. |
| deleteIssue | Delete issue | Deletes an issue. There is no trash. |
| assignIssue | Assign issue | Changes who the issue is assigned to. |
| transitionIssue | Move issue | Moves the issue to another column — a workflow transition. |
| addComment | Add comment | Comments on an issue. |
| getComments | Get comments | Fetches an issue's comments. |
| addAttachment | Attach file | Uploads a file to an issue. |
| addWorklog | Log work | Logs time worked on an issue. |
| linkIssues | Link issues | Links two issues to each other. |
| searchIssues | Search issues (JQL) | Searches issues with JQL. Returns an iterable list. |
Gotchas
- A transition is not a field. You cannot set
statusdirectly — you apply a transition, and only the transitions the workflow allows from the current status are valid. - Transition ids are per project. The id for “Done” in one project is not the id in another; read the available transitions for the issue rather than hardcoding.
- Custom fields are
customfield_NNNNN, not their display name. Their ids differ between sites. - JQL search is paginated and its output is iterable, so a Loop can walk the results.
- Personal data pulled from Atlassian carries reporting obligations — see your Atlassian agreement before storing user records outside Jira.