List Issue Types
jira.list_issue_types
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
List every issue type the connection's account can see.
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
This node takes no configuration beyond its connection.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
issue_types[].id The issue type's id. | string | — |
issue_types[].name The name to pass to jira.create_issue. | string | — |
issue_types[].description The issue type's description. | string | — |
issue_types[].subtask True for a subtask type. | boolean | — |
issue_types[].hierarchyLevel -1 subtask, 0 base, 1 epic. | number | — |
count How many items this call returned. | number | — |
{
"count": 0,
"issue_types": [
{
"description": "",
"hierarchyLevel": 0,
"id": "",
"name": "",
"subtask": false
}
]
}Notes
- Types are site-wide here; a team-managed project may accept only a subset, and names repeat across projects.
See List Issue Types 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.