List Issue Types: Jira action

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.

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

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