Create, update or find Jira issues

Nine Jira steps work with the issues on your Jira site:

• Jira · Create an issue — Opens an issue in a project, with the fields you fill in.
• Jira · Update an issue — Changes the fields you fill in on an issue.
• Jira · Transition an issue — Moves an issue along its workflow — To Do to In Progress.
• Jira · Add a comment — Comments on an issue.
• Jira · Assign an issue — Gives an issue to someone, or unassigns it.
• Jira · Find issues — Issues a JQL search finds, or by project, status, assignee and date.
• Jira · Get an issue — An issue's fields, by its key.
• Jira · Add an attachment — Attaches files from earlier steps to an issue.
• Jira · Link issues — Links two issues — CON-142 blocks CON-120.

Every step except Find issues and Get an issue is tagged Changes data.

Who can do this

Workspace Admins and Editors. Jira is a premium service, marked ◇: on the Free plan its steps say On any paid plan. You can build and test it now; publishing needs a paid plan.

Before you start

A Jira connection in this workspace — see Connect Jira.

Steps

Create an issue:

1. Select + where the step should go. In the step picker, open Apps, select Jira, then Create an issue. Or search Jira.
2. In Connection, choose your Jira connection.
3. In Project, choose the project — Projects you can see in Jira. For example Consulace Ops · CON.
4. In Issue type, choose the type — Task. Sub-task types are marked Sub-task.
5. In Summary, type the summary — Set up Northwind Logistics SSO.
6. Optional:
   • Description — Plain text. A blank line starts a new paragraph.
   • Assignee — someone on the site, Asha Raghunathan · asha@consulace.com. Or an email from an earlier step.
   • Priority — one of the site's priorities.
   • Labels — Separate several with commas. A Jira label has no spaces.
   • Components — Component names, separated with commas.
   • Other fields — the issue type's own fields, required ones first, each with what it takes — number, choice — Low, Medium, High, person — email or account id, sprint id, with · required on those Jira needs. The issue type's own fields, required ones first. A person takes an email or account id, a sprint its id, a date 2026-10-09.
7. Select Run this step to try it. This opens a real issue.

Update an issue:

1. In Issue, the issue's key — The issue's key. For example CON-142, or the key from the step that created or found it.
2. Fill in only what should change — Summary, Description (Replaces the description. Empty leaves it.), Assignee (Empty leaves it. To unassign, use Assign an issue.), Priority, Labels (Replaces its labels. Empty leaves them.), Components (Replaces its components. Empty leaves them.).
3. To change other fields, choose the Project and Issue type — Only to list the fields below. — then fill them in under Other fields. Only the fields you fill in change; a value an earlier step did not give leaves its field as it is.

Transition an issue:

1. In Issue, the issue's key.
2. In Transition, choose the move — The moves open to the issue from where it is. From an earlier step: the transition's name, or the status it leads to. Each shows where it leads — Start progress · → In Progress.
3. Optional: in Comment, a comment — Optional — added with the move.

Add a comment, Assign an issue, Get an issue, Add an attachment:

1. In Issue, the issue's key.
2. For Add a comment, type the Comment — SSO is live.
3. For Assign an issue, choose the Assignee — Or an email from an earlier step. Empty unassigns it.
4. For Add an attachment, choose the File — Files from earlier steps, a line each.

Find issues:

1. Either type Jira's own search in JQL — project = CON AND status = "In Progress" — or leave it empty and use the fields below it. Jira's own search. Leave it empty to search by the fields below.
2. Without JQL, fill in at least one of Project, Status (Status names, separated with commas.), Assignee and Updated since (a date, 2026-10-01).
3. In Most issues, how many at most — Up to 1,000. It starts at 100.

Link issues:

1. In Issue, the first key — CON-142.
2. In Link type, choose the type — each shows its two ways, Blocks · blocks / is blocked by. Read as Issue, the type's outward words, then Linked issue — CON-142 blocks CON-120.
3. In Linked issue, the second key — CON-120.

Every list offers Use a value above it, to give a name, email or id from an earlier step instead; Choose from the list goes back.

Output

Other fields come out as a person reads them: a choice by its value, a person or version by name, rich text as plain text.

Good to know

• Find issues gives one item, with count, the list of issues and the first, most recently updated first. When nothing matches, the run goes down When nothing is found instead, with found set to false — see When a Find step finds nothing.
• Find issues needs something to search by. Jira will not search every issue at once, so give JQL or at least one field.
• The fields come from Jira for the project and issue type you choose, so they match your site's screens. After an admin changes them, select Refresh on Other fields.
• A transition is not a status. Jira allows only the moves its workflow has from the issue's current status, so the list changes from one issue to the next.
• Description and comments are plain text. Line breaks are kept; a blank line starts a new paragraph. Coming out, Jira's formatting is turned back into plain text — lists as - lines, mentions by name.
• Updated since is read in the time zone of the person the connection signs in as, as Jira reads JQL.
• On the Free plan, publishing stops with "“Create an issue” needs a paid plan. Change the plan, or remove it and publish the rest." Tests work on any plan.

If something goes wrong

Related

• Connect Jira
• Start a workflow from Jira issue events
• When a Find step finds nothing
• Premium connections on the Free plan
• Pass files between steps