Jira

Read Jira issues with JQL.

Category: Input
Connection: Jira

What it does

Runs a JQL search against Jira Cloud through a saved Connection and streams the matching issues into the pipeline, following Jira's paging to the end. You choose the search and which issue fields to bring back. Issue fields arrive nested, so they land as dotted columns you can flatten or rename downstream.

Inputs and outputs

Inputs	None. This node starts a pipeline.
Outputs	One.

When to use it

Report on issue throughput, ageing or cycle time
Join delivery data with time tracking or finance data
Export a project's issues to a warehouse on a schedule

Examples

One project

JQL: project = ENG

The simplest useful search: everything in one project.

Open bugs

JQL: type = Bug AND status != Done ORDER BY created DESC

Ordering matters when you also set a record cap.

Chosen fields

Issue fields: summary, status, assignee

Far smaller and faster than Jira's default field set.

Bound a new connection

Max records: 500

Stops after 500 issues while you're still working out the query.

Tips

Jira refuses an unbounded search, so a blank JQL runs the last year's issues (created >= -365d), newest first. Type your own to widen or narrow it.
The credential is an Atlassian API token: it is the password half of Basic auth, with your account email as the username.
Issue fields arrive nested, so they become dotted columns like fields.status.name. Rename them with Manage Columns if they are going somewhere that dislikes dots.
Max records is a real cap: it stops mid-page rather than delivering the rest of the page you were on.
Use “Fetch sample” to fill in the columns so downstream nodes see them without a run.