Count Issues
jira.count_issues
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Count the issues a JQL query matches, without fetching them.
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
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
jql JQL query to count, e.g. 'project = ENG AND status = Done'. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
count How many issues match the query. | number | — |
jql The query that was counted. | string | — |
{
"count": 0,
"jql": ""
}Notes
- Jira's enhanced search (jira.search_issues) no longer reports a result-set total; POST /rest/api/3/search/approximate-count is the endpoint that does. The count is approximate, though in practice exact for small result sets.
See Count Issues 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.