ActionJiraUpdated September 2026

How do I search Jira issues with JQL?

Short answer: You can search issues (jql) in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Search Issues (JQL) action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Search Issues (JQL) in Jira — start free
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 run history shows the failed step with its input and the error message Jira returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Search Issues (JQL) support batch operations?
Run Search Issues (JQL) inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Jira's rate limits.
More actions

Other Jira actions.

Search Issues (JQL) in Jira — start free