Skip to content
ActionJiraUpdated May 2026

How do I search Jira issues with JQL?

Short answer: Drop the "JiraSearch Issues (JQL)" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
JQL Query
jql
stringRequiredJira Query Language expression to filter issues
Max Results
maxResults
stringOptionalMaximum number of issues to return (max 100)
Start At
startAt
stringOptionalIndex of the first result for pagination (0-based)
Fields
fields
stringOptionalComma-separated list of fields to include in response. Leave empty for all.
Sample request
{
"jql": "e.g. project = PROJ AND status = \"In Progress\" ORDER BY created DESC",
"maxResults": "50",
"startAt": "0",
"fields": "e.g. summary,status,assignee,priority"
}
Returns
{
"total": 42,
"issues": [
{
"key": "PROJ-123",
"fields": {
"status": {
"name": "In Progress"
},
"summary": "Fix login redirect",
"priority": {
"name": "High"
}
}
}
],
"startAt": 0,
"maxResults": 50
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Search Issues (JQL).

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Search Issues (JQL).

What does the Search Issues (JQL) action do in Jira?
Searches for issues using JQL (Jira Query Language), the full-featured query syntax. Powers SLA dashboards, segment reports, and complex upsert lookups.
What inputs does Search Issues (JQL) require?
Required: JQL Query. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Jira returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Search Issues (JQL) support batch operations?
Yes. Run Search Issues (JQL) inside a Loop node to process arrays. Tiny Command handles Jira's rate limits automatically so you don't have to throttle manually.
More actions

Other Jira actions.

Send search issues (jql) from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.