Search Issues

jira.search_issues

ActionBusiness appsconnection required

Calls the Jira API GET /rest/api/3/search/jql.

Search Jira issues with a JQL query.

Ask about Jira All Jira nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: Username & password
Providers: Jira
Secret shape: {"email", "api_token"}
Config it needs: domain
Resolved by: config.connection_id, else node.connection_id

Configuration

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
jql JQL query, e.g. 'project=PROJ AND status=Open'.	string	Yes	—	—	—
max_results Max issues (1-100).	number	No	50	≥ 1	—
fields Comma-separated field ids or names to return on each issue, e.g. 'summary,status,assignee'. Defaults to summary and status.	string	No	—	—	—
page_token next_page_token from a previous run, to read the following page.	string	No	—	—	—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_results": 50
}

Output

One shape.

result

Field	Type	Example
issues	array	—
issues[].key The issue key.	string	PROJ-123
issues[].id The issue's numeric id, as a string.	string	—
issues[].summary The issue's summary line.	string	—
issues[].status The issue's current status name.	string	—
issues[].fields Every field the call asked for, as Jira returned it.	object	—
count How many issues this page returned.	number	—
total The page count — Jira's enhanced search no longer reports a result-set total.	number	—
next_page_token Pass back as page_token to read the next page; null on the last.	string	—
is_last True when this is the final page.	boolean	—

{
  "count": 0,
  "is_last": false,
  "issues": [
    {
      "fields": {},
      "id": "",
      "key": "PROJ-123",
      "status": "",
      "summary": ""
    }
  ],
  "next_page_token": "",
  "total": 0
}

Notes

Atlassian removed GET /rest/api/3/search (CHANGE-2046); this node now calls GET /rest/api/3/search/jql. The node type, its config keys and the issues/count/total output keys are unchanged, but the replacement endpoint reports no result-set total, so 'total' is the size of the page returned.
Paging is by next_page_token, not by an offset: feed next_page_token back in as page_token to read the following page.

Related Jira nodes

Templates that use Jira

Solutions with Jira

See Search Issues run in a workflow.

In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demo Talk to sales