Skip to main content
Use Jira to start a flow when work items change in a project, and to work with work items, projects and users from inside a flow. This flow assigns every new bug in the Support project to triage and tells the reporter. Press Run to watch it. Every trigger and node needs a Jira connection. See Connect Atlassian to set one up.

​
Triggers

All three triggers check the project every minute. Only work items and comments created or changed after you turn the trigger on start a flow: what was already in Jira never does. A check starts at most 50 runs, and the rest start on the next check.

​
Nodes

Where a node asks for a user, such as Assignee or Lead, enter their email or their account ID.

​
Troubleshooting

Only work items and comments created or changed after the trigger was turned on start a flow. Check the Project and Work item type filters. With Ignore changes made through this connection on, changes made by the connection’s account are listed in the trigger’s events as Made through this Jira connection.
The trigger reads the connection account’s time zone to search Jira. Set a time zone on that Atlassian account, then check the trigger again.
Too many work items changed at once for the trigger to tell which are new. Narrow it with Work item type, or watch a smaller project.
A key in Work item keys does not exist, or the connection cannot see it. Keys marked invalid key format are not shaped like SUP-42. The other work items are still returned.
The work item cannot move through that transition from its current status. The message lists the transitions it can take; pick one of those.
Jira accepted the transition, but the work item did not show the new status in time. Check the work item’s history in Jira.
The email matches no user, or more than one, or Jira hides that user’s email. Enter the user’s account ID instead.
Bind Cursor to next_cursor from a List Work Items node with the same settings, or leave it empty to start from the first result.
Update Jira Project needs at least one of Name, Lead or Description.
Some files were attached before one failed. Running the node again attaches those files a second time, so remove them from Files first.
The connection’s account lacks permission for this project or action. Create Jira User needs Jira admin rights. See Connect Atlassian.
Check the Jira URL on the connection.