Jira - Search Issues (JQL)
↩ Part of the Jira integration.
Description
Section titled “Description”Runs a JQL query against Jira Cloud (POST /search/jql) and returns the matching issues as an array. It is the entry point for batch automations: pull every open bug, every ticket assigned to a person, everything created yesterday, and process them one by one.
The node returns the issues array directly in data, so it plugs straight into an iterator.
Configuration
Section titled “Configuration”| Field | Type | Required | Description |
|---|---|---|---|
credentials_id | credentials | Yes | Jira credential |
jql | textarea | Yes | JQL query (e.g. project = OPS AND status = "To Do") |
max_results | number | No | Maximum results. Defaults to 50 |
fields | text | No | Comma-separated fields to return (e.g. summary,status) |
jql accepts dynamic variables, so you can build the query from previous nodes. max_results and fields are used as-is; fields is split on commas and sent as an array.
Credentials
Section titled “Credentials”This module requires a Jira (Atlassian) credential:
| Field | Description |
|---|---|
base_url | Site URL, e.g. https://your-domain.atlassian.net |
email | Atlassian account email |
api_token | API token from id.atlassian.com |
Output
Section titled “Output”data is the array of issues (never an object — if there are no matches you get []):
[ { "id": "10042", "key": "OPS-123", "self": "https://your-domain.atlassian.net/rest/api/3/issue/10042", "fields": { "summary": "Checkout returns 500", "status": { "name": "To Do" } } }, { "id": "10043", "key": "OPS-124", "fields": { "summary": "Email receipts not sent", "status": { "name": "To Do" } } }]Along with it, _meta:
{ "moduleVersion": "1.0.0", "success": true, "count": 2, "totalMs": 356 }Usage Example
Section titled “Usage Example”Everything open in a project
Section titled “Everything open in a project”{ "credentials_id": "jira_ops", "jql": "project = OPS AND status = \"To Do\" ORDER BY created DESC", "max_results": 50}Light payload for a report
Section titled “Light payload for a report”{ "credentials_id": "jira_ops", "jql": "project = OPS AND created >= -7d", "max_results": 100, "fields": "summary,status,assignee"}Query built from previous data
Section titled “Query built from previous data”{ "credentials_id": "jira_ops", "jql": "project = OPS AND assignee = \"{{data.account_id}}\" AND resolution = Unresolved"}- Use
ORDER BYinside the JQL to control the order; the node does not sort. max_resultscaps what Jira returns in a single call — the node does not paginate automatically. For large sets, narrow the JQL (for example by date range) and run the node several times.- An invalid JQL comes back as a
validationerror with Jira’s own message, and is not retried. - Quotes inside JQL must be escaped when the value is written in a JSON field, as shown in the examples.
Related Nodes
Section titled “Related Nodes”- Jira: Get issue — read a single issue by key.
- Jira: Update issue — update each result while iterating.
- Jira: Transition issue — bulk-move the issues you found.