Skip to content

Jira

Work with Jira Cloud projects, issues, transitions and comments.
Nodes Jira (actions), Jira Trigger (polling)
Auth Basic (email and API token). Not working yet, see below.
Availability Limited release. Not yet in the palette for customer workspaces.

Known issues: the Jira connector cannot reach Jira Cloud today.

  • Jira Cloud API tokens need HTTP Basic authentication (email plus token). Flero's connector does not send Basic authentication, so requests arrive unauthenticated.
  • The connector has no field for your site name (<site>.atlassian.net), so it cannot build the request address.

Until these are fixed, call the Jira REST API with the HTTP Request node and a Generic credential.

Connecting

There is no "Connect with Jira" OAuth sign-in. The connector's credential takes a username and password, intended for your Atlassian email and an API token.

Operations

Operation What it does
Get all projects Lists projects
Create project Creates a project
Create issue Creates an issue (project, issuetype, summary, description, …)
Get issue Reads an issue by ID or key
Edit issue Updates an issue's fields
Delete issue Deletes an issue
Search for issues using JQL Runs a JQL query (jql, maxResults, startAt)
Get transitions Lists the transitions available for an issue
Transition issue Moves an issue to another status
Get comments Lists an issue's comments
Add comment Adds a comment
Find assignable users Finds users who can be assigned in a project

Enter issue fields as plain fields. Flero wraps them in Jira's fields object.

Triggers

The Jira Trigger polls the list and search operations, every 5 minutes by default. There is no real-time Jira trigger.

Common errors

Symptom Check
401 on every call The known issue above. Use the HTTP Request node.
Requests fail before reaching Jira The site name is missing. Use the HTTP Request node with your full https://<site>.atlassian.net/rest/api/3/... address.

Found something out of date? This page lives in the Flero docs content set.