Jira Node
SkyStudio’s Jira integration allows you to connect your Jira projects directly to your workflows. You can automate all core Jira operations, from issue management and sprint tracking to comments and worklog actions.
🎬 Click to watch the video →
Connection Setup and Management
To use Jira nodes, you must first define a Jira connection. Connections can be reused across all your workflows; after defining one, you only need to select it in each node.
Creating a New Connection
There are two ways to create a connection:
Option 1 — Through the node: Add any Jira node to the canvas, click the Application Connections dropdown, and select Manage Connections.
Option 2 — From the canvas toolbar: Click the Application Connections (🔗) icon in the top toolbar of the workflow editor.
Both methods open the connection form below. Select Jira from the provider list and fill in the following information:
Connection Form Fields
| Field | Required | Description |
|---|---|---|
| Connection Name | Yes | Name you want to give the connection, such as Prod Jira or Test Environment |
| Provider | Yes | Must be selected as Jira |
| Jira Cloud Domain | Yes | Domain of your Atlassian site, such as yourcompany.atlassian.net |
| Yes | Email address of your Atlassian account, such as user@company.com | |
| API Token | Yes | API token generated from your Atlassian account |
How to Get an API Token?
Followid.atlassian.com→ Security → API tokens, create a new token, copy it, and paste it into this field.
After filling in the form and clicking Save, the connection is saved and becomes available in all Jira nodes.
Assigning the Connection to the Node
After creating a connection, you can view and select your defined connections from the Application Connections dropdown in each Jira node.
Once the connection is selected, credentials are automatically merged during execution and testing. The Connection field on the node acts as an optional fallback.
Viewing Active Connections
Click the Active Connections button in the upper-right corner of the canvas to view all tool connections used in the current workflow.
Published workflows run through these connections. For external access scenarios, it is recommended to evaluate which access credentials will apply according to your organizational policies.
Tip: You can type
/in connection fields to insert dynamic values from other nodes in the workflow.
Operations
The SkyStudio Jira node supports the following 14 operations. The first three operations are marked as Featured and are designed for the most common scenarios.
| Operation | Category | Description |
|---|---|---|
| Get Issue | Featured | Retrieves a single issue by ID or key |
| Search Issues (JQL) | Featured | Searches multiple issues using a JQL query |
| Jira AI Assistant | Featured | Queries Jira data using natural language |
| Create Issue | Issue Management | Creates a new Jira issue |
| Change Issue Status | Issue Management | Updates the status of an issue |
| Get Issue Transitions | Issue Management | Lists available status transitions |
| List Projects | Project | Lists all accessible projects |
| Get Project | Project | Retrieves details of a specific project |
| List Boards | Board | Lists project boards |
| Get Sprint Issues | Sprint | Retrieves all issues in a sprint |
| Get Comments | Comment | Lists comments on an issue |
| Add Comment | Comment | Adds a new comment to an issue |
| Get Worklogs | Worklog | Retrieves worklog records for an issue |
| Add Worklog | Worklog | Adds a new worklog record to an issue |
Featured Operations
Get Issue
Retrieves a specific issue in Jira by key. Use it when you want to access all details of a single issue.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Jira key of the issue, such as ENG-123 or PROJ-456 |
| Fields | No | Fields to retrieve, separated by commas, such as summary,status,assignee. If left empty, all fields are returned |
Output
Returns a JSON object containing all requested fields of the issue. It includes standard fields such as summary, status, assignee, priority, description, created, and updated.
Usage Example
Enter ENG-101 in the Issue Key field and summary,status in the Fields field to retrieve only the summary and status information.
Search Issues (JQL)
Filters and lists multiple issues using Jira Query Language, known as JQL. It is ideal for retrieving issues that match specific criteria in bulk.
Input Parameters
| Field | Required | Description |
|---|---|---|
| JQL Query | Yes | JQL query expression, such as project = ENG AND status = 'In Progress' |
| Fields | No | Fields to retrieve, separated by commas, such as summary,status,assignee. If left empty, all fields are returned |
| Get All (Auto Paginate) | No | If enabled, pagination is handled automatically and all results are retrieved at once |
| Limit | No | Maximum number of issues to return. Default: 25 |
Output
Returns an array containing the list of issues that match the JQL query. Each item includes the requested fields.
JQL Examples
project = ENG AND status = "To Do"
assignee = currentUser() AND sprint in openSprints()
project = BUGS AND priority = High AND created >= -7d
labels = "backend" ORDER BY created DESC
Jira AI Assistant
An AI-powered assistant that lets you query your Jira data using natural language. It allows you to run complex queries without knowing JQL.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Query | Yes | Jira question or query written in natural language, such as List the bugs closed this week |
| System Prompt | No | System instruction used to customize the assistant’s behavior. It can add project-specific or company-specific context |
Output
The assistant interprets the query, retrieves the relevant Jira data, and generates a response in natural language format.
Usage Example
Enter "List critical bugs opened in the last 3 days" in the Query field to retrieve related issues without writing any JQL.
Issue Management
Create Issue
Creates a new issue in Jira. It can be used in automatic bug tracking, task generation, or support request workflows.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Project Key | Yes | Key of the project where the issue will be created, such as ENG or BUGS |
| Summary | Yes | Issue title or summary |
| Issue Type | Yes | Issue type, such as Bug, Task, Story, or Epic |
| Description | No | Detailed description of the issue |
| Assignee Account ID | No | Jira account ID of the user to assign |
| Priority | No | Priority level: Highest, High, Medium, Low, or Lowest |
| Labels | No | Labels to add to the issue, separated by commas, such as backend,urgent |
Output
Returns a JSON object containing the created issue’s id, key, and self URL.
Change Issue Status
Updates the status of an existing issue. It is used to automate workflow transitions.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue whose status will be changed, such as ENG-123 |
| Transition ID | Yes | ID of the transition to apply. Use the Get Issue Transitions operation to find available transition IDs |
Output
Returns an empty response after a successful operation, HTTP 204.
Tip: If you do not know the Transition ID, first run Get Issue Transitions to list available transitions and IDs for the relevant issue.
Get Issue Transitions
Lists available status transitions and transition IDs for an issue. It is used before the Change Issue Status operation.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue whose transitions will be queried, such as ENG-123 |
Output
Returns an array containing id, name, such as "In Progress" or "Done", and to, the target status, for each transition.
Project Operations
List Projects
Lists all projects accessible by the connected Jira account.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Get All (Auto Paginate) | No | If enabled, all projects are retrieved with automatic pagination |
| Limit | No | Maximum number of projects to return |
Output
Returns an array containing id, key, name, and projectTypeKey information for each project.
Get Project
Retrieves details of a specific project by key.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Project Key | Yes | Key of the project to query, such as ENG or PROJ |
Output
Returns a JSON object containing the project’s id, key, name, description, lead, and configuration information.
Board Operations
List Boards
Lists Scrum or Kanban boards belonging to a project.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Project Key | No | Key of the project to filter by, such as ENG. If left empty, all boards are listed |
| Limit | No | Maximum number of boards to return. Default: 50 |
Output
Returns an array containing id, name, and type, such as scrum or kanban, for each board.
Sprint Operations
Get Sprint Issues
Lists all issues belonging to a specific sprint. It is used for sprint-based reporting and automation.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Sprint ID | Yes | Jira ID of the sprint to query, as a numeric value, such as 42 |
| Get All (Auto Paginate) | No | If enabled, all issues are retrieved with automatic pagination |
| Limit | No | Maximum number of issues to return. Default: 50 |
Output
Returns an array containing the list of issues belonging to the sprint.
Comment Operations
Get Comments
Lists all comments added to an issue.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue whose comments will be retrieved, such as ENG-123 |
| Limit | No | Maximum number of comments to return |
Output
Returns an array containing id, author, body, and created information for each comment.
Add Comment
Adds a new comment to an existing issue. It can be used to send notifications, update status, or leave notes.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue where the comment will be added, such as ENG-123 |
| Comment | Yes | Comment content. Plain text or Jira formatting is supported |
Output
Returns a JSON object containing the created comment’s id, author, body, and created information.
Worklog Operations
Get Worklogs
Lists all time tracking, or worklog, records saved on an issue.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue whose worklog records will be retrieved, such as ENG-123 |
Output
Returns an array containing id, author, timeSpent, timeSpentSeconds, and started, the start date, for each worklog record.
Add Worklog
Adds a new time tracking record to an issue. It is used to automatically log working time.
Input Parameters
| Field | Required | Description |
|---|---|---|
| Issue Key | Yes | Key of the issue where the worklog will be added, such as ENG-123 |
| Time Spent | Yes | Time spent in Jira format, such as 2h 30m, 1d, or 45m |
| Comment | No | Note or description to add to the worklog |
| Started At | No | Date and time when the work started, in ISO 8601 format, such as 2024-04-14T09:00:00.000+0000. If left empty, the current time is used |
Output
Returns a JSON object containing the created worklog record’s id, author, timeSpent, timeSpentSeconds, and started information.
Quick Start Examples
Example 1: Bug Automation
Automatically create a Jira issue from bug information received through a form:
- Get bug information from the user with the Text Input node.
- Connect it to the Create Issue node and set
Project Key: BUGS,Issue Type: Bug, andPriority: High. - Add source information to the created issue with the Add Comment node.
Example 2: Sprint Status Report
Report the status of all issues in the active sprint:
- Enter the sprint ID with the Get Sprint Issues node.
- Summarize the data using the Jira AI Assistant or Data Analysis node.
- Send the report to the user with Text Output.
Example 3: Automatic Worklog
Automatically create a time log when a task is completed:
- Move the issue to
Doneusing the Change Issue Status node. - Save
Time Spent: 1handComment: Automatically completedwith the Add Worklog node.
Common Errors
| Error | Possible Cause | Solution |
|---|---|---|
404 Issue not found | Incorrect Issue Key entered | Check that the Issue Key is in the correct format, such as ENG-123 |
400 Invalid JQL | JQL query is incorrect | Test the JQL syntax in Jira |
403 Forbidden | Insufficient permissions | Verify that the connected account has permission for the related project |
Transition not found | Invalid Transition ID | First list available transitions using Get Issue Transitions |