ActionJiraUpdated September 2026

How do I list every Jira issue status?

Short answer: You can list statuses in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira List Statuses action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Statuses in Jira — start free All 17 Jira actions

List Statuses in Jira — start free

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

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