JIRA GET ISSUE¶
Fetches a specific Jira issue by key and extracts all important fields including summary, description, dates, assignee, reporter, status, priority, issue type, project, and attachments. Use this worker to pull structured Jira issue data into a d3VIEW workflow for downstream processing, reporting, or decision logic.
When to use¶
Tagged: atlassian, integration, issue, jira, project-management, rest-api, ticket.
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 http:// or 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 instead of a password for secure authentication. |
| Issue Key | issue_key | text | — | ✓ | Jira issue key identifying the ticket to fetch (e.g., PROJ-123); must match an existing issue in the target Jira instance. |
| Expand Options | expand | text | — | Optional comma-separated list of Jira API expand options to include additional data in the response (e.g., changelog,names,schema); leave blank for the default field set. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Status | status | text | Operation result indicator; returns ‘success’ on a successful API call or an ‘Error: …’ message string on failure. |
| Issue Key | issue_key | text | The Jira issue key as confirmed by the API response (e.g., PROJ-123); useful for chaining downstream workers. |
| Summary | summary | text | The one-line title/summary of the Jira issue as stored in the ‘summary’ field. |
| Description | description | json | The full issue description serialised as an Atlassian Document Format (ADF) JSON string; empty string if no description is set. |
| Description Text | description_text | text | Plain-text rendition of the issue description extracted from the ADF structure; suitable for display or NLP processing. |
| Created Date | created_date | text | ISO 8601 timestamp of when the issue was created (e.g., 2024-01-15T08:30:00.000+0000). |
| Due Date | due_date | text | Due date for the issue in YYYY-MM-DD format; empty string if no due date has been set. |
| Assignee | assignee | text | Display name of the user currently assigned to the issue; returns ‘Unassigned’ if no assignee is set. |
| Reporter | reporter | text | Display name of the user who created or reported the issue. |
| Status | status | text | Operation result indicator; returns ‘success’ on a successful API call or an ‘Error: …’ message string on failure. |
| Priority | priority | text | Priority level of the issue as a string (e.g., ‘High’, ‘Medium’, ‘Low’); empty string if not set. |
| Issue Type | issue_type | text | Jira issue type name (e.g., ‘Bug’, ‘Story’, ‘Task’); empty string if not available. |
| Project Key | project_key | text | Short key of the Jira project the issue belongs to (e.g., ‘PROJ’). |
| Project Name | project_name | text | Full display name of the Jira project the issue belongs to. |
| Attachment IDs | attachment_ids | text | Comma-separated list of Jira attachment IDs associated with the issue; empty string if there are no attachments. |
| Attachment Filenames | attachment_filenames | text | Comma-separated list of filenames for all attachments on the issue; empty string if there are no attachments. |
| Raw Response | raw_response | json | Complete JSON response object returned by the Jira REST API for the issue; useful for extracting custom or non-standard fields not covered by the named outputs. |
Disciplines¶
- platform.integration
Auto-generated from platform schema. Worker id: jira_get_issue. Schema hash: 4d365de3de3f. Hand-curated docs in workerexamples/ override this page when present.