ActionJiraUpdated September 2026

How do I list every Jira issue type?

Short answer: You can list issue types in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira List Issue Types 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 Issue Types in Jira — start free All 17 Jira actions

List Issue Types in Jira — start free

Sample request

{}

Returns

[
  {
    "id": "1",
    "name": "Bug",
    "description": "A problem which impairs functionality"
  },
  {
    "id": "2",
    "name": "Story",
    "description": "A user story"
  },
  {
    "id": "3",
    "name": "Task",
    "description": "A small task"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Issue Types.

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 Issue Types.

What does the List Issue Types action do in Jira?

Lists all issue types available in Jira (Story, Task, Bug, Epic, custom types). Use to populate a type picker before creating an issue.

What inputs does List Issue Types require?

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

Run List Issue Types 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