JIRA SEARCH ISSUES¶
Executes a JQL (Jira Query Language) query against a Jira Cloud instance and returns matching issues as a structured dataset. Use this worker to pull issue lists, statuses, assignments, or any filterable Jira data into a d3VIEW workflow.
When to use¶
Tagged: atlassian, integration, issue_search, jira, jql, rest_api.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Jira Instance URL | jira_url | text | — | ✓ | Base URL of your Jira Cloud instance (e.g., https://yourorg.atlassian.net); must begin with https:// and must not include a trailing slash. |
| User Email | text | — | ✓ | Atlassian account email address used for Basic Auth; must match the account that owns the API token. | |
| API Token | api_token | text | — | ✓ | Atlassian API token (generated at id.atlassian.com) used for authentication; do not use your account password here. |
| JQL Query | jql_query | textarea | — | ✓ | Full JQL query string that filters the issues to retrieve (e.g., ‘project = PROJ AND status = Open AND assignee = currentUser()’); supports the Jira code editor. |
| Fields to Return | fields | text | — | Optional comma-separated list of Jira field keys to include in each returned issue (e.g., summary,status,assignee,priority); leave blank to receive the Jira API default field set. | |
| Expand Options | expand | text | — | Optional comma-separated list of Jira API expand directives that augment the response payload (e.g., changelog,names,schema); leave blank unless additional metadata is required. | |
| Max Results | max_results | number | 50 | Maximum number of issues to return in a single call (integer 1–1000, default 50); capped at 1000 regardless of the value provided. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Status | status | text | Human-readable outcome string; contains ‘Success: Found N issue(s).’ on success or an error message prefixed with ‘Error:’ on failure. |
| Results | results | dataset | Flat dataset (array of associative arrays) where each row represents one Jira issue with top-level fields (id, key, self) and all requested or default fields expanded as columns. |
| Summary | summary | text | Multi-line text block reporting the executed JQL query, total issues matching the query on the server, issues actually returned, pagination start index, and the effective max-results limit. |
Disciplines¶
- platform.integration
Auto-generated from platform schema. Worker id: jira_search_issues. Schema hash: 1b59eee00c0e. Hand-curated docs in workerexamples/ override this page when present.