Jira Action Block
The Jira Action Block manages issues, comments, sprints, and projects in Jira from your workflow — create bugs automatically, move issues through statuses, assign work, and search with JQL.
Issue Automation: Pair this block with the Jira Trigger to react when issues are created or updated in Jira, and use this block to act on them.
Key Features
- 17 Operations covering issues, comments, projects, boards, sprints, and users
- Cloud and Server: Works with Jira Cloud (API token), Jira Server (password), and Jira Server with a Personal Access Token
- JQL Search: Find issues with full Jira Query Language
- Workflow Transitions: Move issues between statuses (e.g. To Do → In Progress → Done)
- Save Any Value: Map response fields (Issue Key, Status, Assignee, and more) into workflow variables
Operations
| Group | Operations |
|---|---|
| Issues | Create Issue, Update Issue, Get Issue, Search Issues, Delete Issue, Assign Issue, Transition Issue |
| Comments | Add Comment, Update Comment, Get Comments |
| Projects | Get Projects, Get Project |
| Boards & Sprints | Get Boards, Get Sprints, Move to Sprint |
| Users | Get Users, Get Current User |
Configuration
| Parameter | Used by | Description |
|---|---|---|
| Project Key | Create Issue, Get Project | e.g. PROJ |
| Issue Type | Create Issue | e.g. Bug, Task, Story |
| Summary / Description | Create/Update Issue | Issue title and body |
| Priority, Assignee, Labels | Create/Update/Assign Issue | Standard issue fields |
| Issue Key | Get/Update/Delete/Assign/Transition, Comments | e.g. PROJ-123 |
| Transition ID | Transition Issue | The id of the target status transition |
| JQL | Search Issues | Jira Query Language, e.g. project = PROJ AND status = "To Do" |
| Max Results | Search Issues | Number of results (default 50) |
| Board ID / Sprint ID | Boards & Sprints | Targets for sprint operations |
| Custom Fields | Create/Update Issue | Key/value map of custom field ids |
Connecting Jira
- Add the Jira block to your workflow and open its settings.
- Click to add a new Jira connection and enter:
- Domain — your Jira URL, e.g.
your-team.atlassian.net - Email — the Atlassian account email (Cloud)
- API Token — created at id.atlassian.com/manage-profile/security/api-tokens (opens in a new tab)
- Domain — your Jira URL, e.g.
- Choose the matching Jira version:
- Cloud — Email + API Token
- Server — Email/username + Password
- Server (PAT) — Personal Access Token
- Save and select the credential in the block.
⚠️
For Jira Cloud, use an API token, not your account password — Atlassian blocks basic auth with passwords on Cloud.
Saving output to variables
Use Response Mapping to store parts of the result in variables:
Issue ID, Issue Key, Issue Summary, Issue Status, Issue Assignee, Issue Reporter, Issue Priority, Issue Type, Project Key, Project Name, Comment ID, Sprint ID, Sprint Name, Board ID, Created Date, Updated Date, or Full Response.
Example: Bug report from a form
- Typeform Trigger — fires when a customer submits a bug report form.
- Jira (Create Issue) — creates a
Bugin projectSUPwith the form answers as summary and description; the new Issue Key is saved to a variable. - Jira (Assign Issue) — assigns it to the on-call engineer.
- Slack — posts the issue key and link to the team channel.
Related
- Jira Trigger — start a workflow when something happens in Jira