ActionJiraUpdated May 2026

How do I list every Jira issue status?

Short answer: Drop the "Jira → List Statuses" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 17 Jira actions

Sample request

{}

Returns

[
  {
    "id": "10001",
    "name": "To Do",
    "statusCategory": {
      "id": 2,
      "key": "new",
      "name": "To Do"
    }
  },
  {
    "id": "10002",
    "name": "In Progress",
    "statusCategory": {
      "id": 4,
      "key": "indeterminate",
      "name": "In Progress"
    }
  },
  {
    "id": "10003",
    "name": "Done",
    "statusCategory": {
      "id": 3,
      "key": "done",
      "name": "Done"
    }
  }
]

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

Triggered by

Apps that pair well as the trigger for List Statuses.

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

2 Google Sheets triggers

HubSpot → Jira

18 HubSpot triggers

FAQ

Questions about List Statuses.

What does the List Statuses action do in Jira?

Returns all issue statuses available in the Jira instance with their categories. Useful for filtering and for validating status names before a transition.

What inputs does List Statuses require?

List Statuses has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Statuses support batch operations?

Yes. Run List Statuses 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