Jira
Automate issue tracking, sprint management, and project workflows — create issues from alerts, transition statuses, manage sprints, and query with JQL from any BizFirst workflow.
What this node does: The Jira node provides full Jira REST API coverage across four resources: issue (7 operations), project (3 operations), user (2 operations), and sprint (4 operations, Jira Software only). All operations authenticate via API Token against your Jira Cloud or Server instance. Use JQL (Jira Query Language) for powerful, expressive issue searches across any combination of fields.
Resources & Operations (16 total)
issue 7 Operations
| Operation | Description |
|---|---|
issue/create | Create a new Jira issue (Bug, Task, Story, Epic, or Subtask) with full field support including description, priority, assignee, labels, components, and custom fields. |
issue/get | Retrieve a complete issue object by its key (e.g. ENG-142). Returns all fields, status, assignee, comments count, and linked issues. |
issue/getMany | Search for multiple issues using a JQL query string. Supports field selection and pagination. |
issue/update | Update one or more fields on an existing issue. Only specified fields are changed; all other fields are preserved. |
issue/delete | Permanently delete an issue by key. Optionally deletes all subtasks along with the parent issue. |
issue/addComment | Add a comment to an issue. Supports plain text or Atlassian Document Format (ADF) for rich-text comments with mentions, code blocks, and panels. |
issue/transition | Move an issue through its workflow by transition name (e.g. "In Progress", "In Review", "Done"). The node resolves the transition name to the correct transition ID automatically. |
project 3 Operations
| Operation | Description |
|---|---|
project/get | Retrieve details for a single project by its key, including name, description, project type, lead, and issue type schemes. |
project/getMany | List all Jira projects accessible to the authenticated user. Returns project keys, names, and types. |
project/getStatuses | Get all available statuses for each issue type in a project. Use this to discover valid transition names for issue/transition. |
user 2 Operations
| Operation | Description |
|---|---|
user/get | Retrieve a user's profile by their Jira account ID. Returns display name, email, avatar, and active status. |
user/search | Search for Jira users by name or email address. Returns matching user objects including their account IDs for use in issue assignment. |
sprint 4 Operations (Jira Software)
| Operation | Description |
|---|---|
sprint/create | Create a new sprint on a Jira Software board. Set the sprint name, start date, end date, and goal. |
sprint/get | Retrieve a sprint by its ID. Returns name, state (active/closed/future), start date, end date, and goal. |
sprint/getMany | List all sprints for a Jira Software board. Filter by state: active, closed, or future. |
sprint/addIssues | Move one or more issues to a specified sprint by passing an array of issue keys. |
Key Use Cases
- Automated issue creation from alerts: When a monitoring system detects a production error, a webhook triggers a BizFirst workflow that creates a Jira Bug issue with error details, stack trace, and severity level — all pre-populated and assigned to the on-call engineer.
- Sprint management: At the start of each sprint cycle, automatically create the sprint, move prioritised stories from the backlog using JQL queries, and post a sprint kickoff summary to Slack.
- Deployment tracking: When a deployment pipeline completes, add a structured comment to the relevant Jira release issue with deployment details, environment, version, and a link to the deployment log.
- PR-to-issue status sync: When a pull request is opened in GitHub, automatically transition the linked Jira issue from "To Do" to "In Review" without manual status updates.
- Compliance and audit trails: Query all closed bugs in a project for a reporting period using JQL, compile a summary, and generate a compliance report stored in Notion or emailed to stakeholders.
Authentication Setup
API Token, not password: Jira Cloud requires an API Token for authentication — your Atlassian account password is not accepted. Generate an API token at id.atlassian.com/manage-profile/security/api-tokens. Use your Atlassian account email as the
Email field. For Jira Server/Data Center, use a Personal Access Token instead.
Three authentication properties are required for every operation:
- InstanceUrl: Your full Jira base URL, e.g.
https://yourorg.atlassian.netfor Jira Cloud orhttps://jira.yourcompany.comfor Jira Server. No trailing slash. - Email: The email address associated with your Atlassian account (Cloud) or Jira username (Server).
- ApiToken: The API token generated from your Atlassian security settings. Store this in BizFirst Credentials Manager.
In This Guide
Configuration
Complete property reference for all 16 operations. Includes JQL syntax guide and Atlassian Document Format notes for rich comment bodies.
Input & Output
Issue object schema, JQL search results format, transition response, and output ports.
Examples
Five real-world examples: bug from alert, JQL sprint search, PR-triggered transition, deployment comment, and sprint creation with backlog move.