List Backlog Issues

jira.list_backlog_issues

ActionBusiness appsconnection required

Calls the Jira Cloud REST API with the connection's email and API token.

List the issues sitting in a Jira Software board's backlog.

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

5 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
board_id The board's numeric id — list boards with jira.list_boards.	string	Yes	—	—	10021
jql Narrow the backlog with a JQL fragment, e.g. 'labels = urgent'.	string	No	—	—	—
fields Comma-separated field ids or names to return on each issue.	string	No	—	—	—
max_results Maximum results to return in one call.	number	No	50	≥ 1	—
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.

{
  "board_id": "10021",
  "max_results": 50
}

Output

One shape.

result

Field	Type	Example
issues[].id The issue's numeric id, as a string.	string	—
issues[].key The issue key.	string	PROJ-123
issues[].fields.summary The issue's summary line.	string	—
issues[].fields.status.name The issue's current status.	string	—
count How many items this call returned.	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 of results.	boolean	—

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

Notes

Boards, sprints and the backlog are Jira Software's API (/rest/agile/1.0), not the platform API — they exist only on a site with Jira Software, and only company-managed and team-managed software projects have boards.
The backlog holds incomplete issues that are in no active or future sprint.
Atlassian removed the offset-paged /rest/agile/1.0 backlog endpoint after 2026-11-01; this node calls its replacement, GET /rest/software/1.0/board/{boardId}/backlog, which pages by next_page_token and reports no result-set total. 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 List Backlog 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