Jira Node — BizFirstAI

24 operations across 5 resources: The Jira node covers Issue (9 ops), Comment (5 ops), Attachment (4 ops), Project (2 ops), and User (3 ops). All operations authenticate via Atlassian API Token. Compatible with Jira Cloud and Jira Server/Data Center.

Issue — 9 Operations

issue/create

Create a new issue (Bug, Task, Story, Epic, Sub-task) with full field support, priorities, labels, and custom fields.

issue/get

Retrieve a complete issue by key (e.g. PROJ-123). Returns all fields, current status, assignee, and metadata.

issue/getAll

Search issues using JQL with pagination. Supports complex queries across projects, assignees, dates, and custom fields.

issue/update

Update one or more fields on an existing issue. Only specified fields are changed; all others are preserved.

issue/delete

Permanently delete an issue by key. Irreversible — use with a confirmation guard in your workflow.

issue/getTransitions

List all workflow transitions available for an issue in its current state. Required before calling executeTransition.

issue/executeTransition

Move an issue through its workflow by transition ID. Optionally set fields required by the transition screen.

issue/getChangelog

Retrieve the full field-change history for an issue. Useful for audit trails and compliance reporting.

issue/notify

Send an email notification for an issue to a specified set of users with a custom subject and message body.

Comment — 5 Operations

comment/add

Add a comment to any issue. Supports plain text. Use for automated status updates, deployment notes, and audit entries.

comment/get

Retrieve a single comment by its ID from a specific issue. Returns author, body, and timestamps.

comment/getAll

List all comments on an issue. Returns author, body, and timestamps for each entry.

comment/update

Edit the body of an existing comment. Replaces the full comment body with the new text provided.

comment/remove

Delete a comment from an issue by ID. Permanent — cannot be undone via the API.

Attachment — 4 Operations

attachment/add

Upload a file to a Jira issue. Attach logs, screenshots, reports, or any binary file by providing a local file path.

attachment/get

Retrieve metadata for a specific attachment by ID. Returns file name, size, MIME type, and author.

attachment/getAll

List all attachments on an issue. Returns metadata array with file names, sizes, and download URLs.

attachment/remove

Delete an attachment by ID. Removes the file from Jira storage permanently.

Project — 2 Operations

project/list

List all Jira projects accessible to the authenticated user. Returns keys, names, types, and lead information.

project/get

Get full details for a specific project by its key, including description, type, lead, and self URL.

User — 3 Operations

user/create

Create a new Jira user with email address, display name, and optional username. Sends invitation email.

user/get

Retrieve a user profile by username. Returns display name, email, account status, and account ID.

user/delete

Delete a Jira user account. Irreversible action — requires appropriate admin permissions.

Authentication

API Token required — not your password. Jira Cloud does not accept account passwords via the REST API. You must generate an API token at id.atlassian.com/manage-profile/security/api-tokens. Store the token in BizFirst Credentials Manager — never embed it directly in node configuration.

Every Jira node operation requires these three connection fields:

Field	Required	Description
`Host`	Required	Your Jira instance base URL. For Jira Cloud: `https://yourcompany.atlassian.net`. For Jira Server: `https://jira.yourcompany.com`. No trailing slash.
`Email`	Required	The email address of your Atlassian account (Cloud) or Jira username (Server/DC). Used as the HTTP Basic Auth username.
`ApiToken`	Required	API token from Atlassian security settings. Used as the HTTP Basic Auth password. Store via Credentials Manager — reference as `{{ $credentials.jiraToken }}`.

Key Use Cases

Alert-driven bug creation: A Datadog monitor fires on a P1 error — a BizFirst workflow triggers issue/create with the error message, stack trace, affected service, and environment automatically populated in the description. The issue is assigned to the on-call engineer and a Slack alert is posted with the issue key.
CI/CD pipeline integration: When a GitHub Actions deployment fails, the pipeline calls a BizFirst webhook that creates a Jira incident with build log attachments, transitions it to "In Progress", and assigns it to the deploying developer.
Sprint lifecycle automation: At sprint start, a scheduled workflow queries the backlog with JQL, creates the sprint, moves the top-priority stories, and posts a sprint summary to the team Slack channel.
Compliance audit trail: Every infrastructure change in a regulated environment triggers a BizFirst workflow that creates a Jira task with who changed what, when, and why — satisfying SOC 2 change management controls.
Support ticket escalation: When a customer support ticket in Zendesk exceeds SLA thresholds, an automation creates a high-priority Jira issue, links it to the support ticket, notifies the engineering team, and logs the escalation as a comment on the Jira issue.

Rate Limits

Jira Cloud rate limit: Approximately 50 requests per 10 seconds per user account. For bulk workflows, use issue/getAll with pagination rather than looping individual issue/get calls. Consider using a dedicated service account so automation traffic does not compete with user API calls.