Description
The Jira Issues activity enables seamless integration with Jira’s issue management API. You can perform a variety of operations on Jira issues—such as creating, reading, updating, deleting, or querying them—directly from within a workflow. This makes it ideal for automating DevOps tasks, managing agile boards, reporting bugs, or syncing task statuses across systems.
Supported operations include:
- Create / Create Many: Add one or more issues into a Jira project.
- Update: Modify details of an existing issue.
- Delete: Remove an issue or its subtasks.
- Get / Get All: Retrieve details of a specific issue or all issues under a project.
- Query: Use JQL (Jira Query Language) to fetch filtered issues.
Use Case Example: A QA team member submits a bug via a form, triggering a workflow that automatically creates a Jira issue under a QA-Bugs project with all the captured details, assigns it to a developer, and adds a label auto-generated.
| Type | Description |
|---|
| Data | Required for Create Many. Optional or not applicable for other operations. |
Output
| Type | Description |
|---|
| Data | Output contains details of the issue(s) affected by the selected operation, returned as JSON. |
Example fields:
key – Unique issue key (e.g., PROJ-123)id – Internal issue IDfields.summary – Issue summaryfields.assignee – Assigned userfields.status – Current issue status
Configuration Fields
| Field | Description | Required |
|---|
| Connection | Jira OAuth connection used to authenticate and authorize API access. | Required |
| Site Name | The Jira Cloud site domain (e.g., your-company.atlassian.net). | Yes |
| Cloud ID | Jira Cloud instance ID (automatically handled with connection). | Yes |
| Operation | The action to perform: Create, Create Many, Update, Delete, Get, Get All, or Query. | Yes |
| Issue Key | Key of the issue (e.g., PROJ-101). Used for operations like Get, Update, or Delete. | Yes |
| Project | The Jira project key (e.g., PROJ). Required for Create, Create Many, or Get All. | Yes |
| Issue Type | The type of issue to create or update (e.g., Task, Bug, Story). | Optional |
| Summary | A short description of the issue (required when creating or updating an issue). | Optional |
| Assignee | Jira username or account ID to assign the issue to. Used for Create or Update. | Optional |
| Description | Long text describing the issue in detail. Applicable for Create and Update. | Optional |
| Parent Issue Key | Used when creating a subtask under a parent issue. | Optional |
| Priority | Priority level of the issue (e.g., High, Medium, Low). Used in Create or Update. | Optional |
| Reporter | User who reported the issue. Can be auto-assigned or explicitly provided. | Optional |
| Custom Field | Any custom fields defined in your Jira schema (e.g., customfield_10010: "Release-1.0"). | Optional |
| Delete Subtask | Option to delete subtasks along with the main issue. Applicable to Delete operation. | Optional |
| JQL | Jira Query Language string used in Query operation to filter issues (e.g., status = "In Progress"). | Optional |
| Field | Value |
|---|
| Summary | Fix login crash on mobile |
| Issue Type | Bug |
| Description | App crashes when login is attempted with expired token. |
| Project | MOBILE |
| Assignee | dev.jane |
| Priority | High |
Sample Configuration
| Field | Value |
|---|
| Connection | Jira OAuth |
| Site Name | your-company.atlassian.net |
| Operation | Create |
| Project | MOBILE |
| Issue Type | Bug |
| Summary | Fix login crash on mobile |
| Description | App crashes with expired token |
| Priority | High |
| Assignee | dev.jane |
Sample Output
Notes
- For
Create Many, the input must contain a list of issues with their respective metadata.
- Jira permissions must allow API access for the connected user.
- You can chain this activity with transitions, webhooks, or comment activities to fully automate issue management.
