Jira

Connect Collabase to Jira to create issues from bugs or test failures, update status, transition issues through workflows, and attach files — triggered by Jira webhook events.

Authentication

Auth type: Basic (email + API token) Generate an API token at id.atlassian.com/manage-profile/security/api-tokens.

Credential	Description
Email	Your Atlassian account email
API Token	Your Atlassian API token
Base URL	Your Jira instance URL (e.g. `https://yourcompany.atlassian.net`)

Triggers

Trigger	When it fires
Issue Created	A new Jira issue is created in any project
Issue Updated	An issue’s status, fields, or assignee change
Issue Resolved	An issue is transitioned to a resolved status
Sprint Started	A sprint is activated
Sprint Completed	A sprint is closed

Actions

Action	Key inputs	Key outputs
Create Issue	`projectKey`, `summary`, `issueType`, `description`, `priority`, `assigneeEmail`, `labels[]`	id, key, url
Get Issue	`issueKey`	id, key, summary, status, assignee, priority
Update Issue	`issueKey`, `summary`, `priority`, `assigneeEmail`, `description`	success
Transition Issue	`issueKey`, `transitionId`	success
Search Issues (JQL)	`jql`, `maxResults`	issues[] — id, key, summary, status
Add Comment	`issueKey`, `body`	id
Attach File	`issueKey`, `fileUrl`, `filename`	attachmentId

Find valid transition IDs via the Jira REST API: GET /rest/api/3/issue/{issueKey}/transitions. Common IDs: 11 = To Do, 21 = In Progress, 31 = Done (these vary per project workflow).

Last modified on April 2, 2026