Jira Integration
Connect Plura AI with Jira to automate issue creation, status updates, work logging, and team collaboration.Overview
The Jira integration enables your AI agents to interact with Jira’s issue tracking and project management capabilities. Create issues from conversations, update statuses, assign tasks, log work time, search for issues, and add comments—all without leaving your workflow.Supports both API Token (Basic Auth) and OAuth 2.0 authentication methods for maximum flexibility.
Authentication
The Jira integration supports two authentication methods:API Token (Basic Auth)
Recommended for server-to-server integrations and internal workflows. Required Parameters:apiKey— Your Jira API token (Generate here)email— Your Jira account email addressinstanceUrl— Your Jira instance URL (e.g.,https://your-domain.atlassian.net)
OAuth 2.0
Recommended for user-facing integrations where users authenticate with their own Jira accounts. Required Parameters:userId— User identifier (instanceUrl retrieved automatically from token metadata)
Available Actions
The Jira integration supports six core automation actions:| Action | Description | Use Case |
|---|---|---|
create_issue | Create new Jira issues | Log bugs, create tasks from conversations |
update_status | Transition issues between statuses | Move issues through workflow stages |
assign_issue | Assign issues to team members | Distribute work based on conversation context |
log_work | Log time spent on issues | Track work automatically from conversations |
search_issues | Search and filter issues | Find relevant issues based on criteria |
add_comment | Add comments to issues | Update issues with conversation context |
Action 1: Create Issue
Create new Jira issues with full field support including custom fields.Supported Issue Types
- Task — General work items
- Bug — Software defects and issues
- Feature — New feature requests
- Story — User stories (Agile)
Basic Example
With Priority and Assignment
OAuth Example
Required Fields
| Field | Type | Description |
|---|---|---|
project.key or project.id | string | Project identifier |
issuetype.name | string | Task, Bug, Feature, or Story |
summary | string | Issue title |
Optional Fields
| Field | Type | Options | Description |
|---|---|---|---|
description | string | — | Detailed description |
priority.name | string | Highest, High, Medium, Low, Lowest | Priority level |
assignee.emailAddress | string | — | Assignee email |
assignee.accountId | string | — | Jira account ID |
assignee.displayName | string | — | Display name |
customFields | object | — | Custom field key-value pairs |
Action 2: Update Status
Transition issues through your Jira workflow by specifying transition IDs.Example
Required Fields
| Field | Type | Description |
|---|---|---|
issueId | string | Issue key (e.g., PROJ-123) |
transitionId | string | Numeric transition ID |
Finding Transition IDs: Use the Jira API
/rest/api/3/issue/{issueKey}/transitions to retrieve available transitions for an issue.Action 3: Assign Issue
Assign issues to team members by email address or account ID.Assign by Email
Assign by Account ID
Required Fields
| Field | Type | Description |
|---|---|---|
issueId | string | Issue key |
assignee.emailAddress or assignee.accountId | string | User identifier |
Action 4: Log Work
Track time spent on issues with optional comments and start timestamps.With Comment and Start Time
Minimal Example
Time Format
Jira supports flexible time formats:- Minutes:
30m,45m - Hours:
2h,3h 30m - Days:
1d,2d - Weeks:
1w,2w - Combined:
2h 30m,1d 4h
Required Fields
| Field | Type | Description |
|---|---|---|
issueId | string | Issue key |
timeSpent | string | Time in Jira format |
Optional Fields
| Field | Type | Description |
|---|---|---|
comment | string | Work log description |
started | string | ISO 8601 timestamp |
Action 5: Search Issues
Search and filter issues using multiple criteria with pagination support.Multiple Filters
Search by Status
Search by Assignee
Filter Options
| Parameter | Type | Description |
|---|---|---|
status | string | Filter by status name |
priority | string | Highest, High, Medium, Low, Lowest |
project | string | Project key |
assignee | string | Email or account ID |
reporter | string | Email or account ID |
maxResults | integer | Results per page (1-100, default: 50) |
startAt | integer | Pagination offset (default: 0) |
Action 6: Add Comment
Add comments to issues with optional visibility restrictions.Basic Comment
Comment with Visibility
Required Fields
| Field | Type | Description |
|---|---|---|
issueId | string | Issue key |
body | string | Comment text |
Optional Fields
| Field | Type | Description |
|---|---|---|
visibility.type | string | role or group |
visibility.value | string | Role or group name |
Response Format
All Jira actions return a consistent response structure:Success Response
Error Response
Common Use Cases
Bug Tracking from Conversations
Automatically create bug issues when users report problems during conversations, with full context captured.
Task Assignment
Route issues to appropriate team members based on conversation analysis and expertise mapping.
Status Updates
Progress issues through workflows automatically based on conversation milestones and confirmations.
Work Time Tracking
Log time spent on issues directly from conversation interactions and agent activities.
Error Handling
| Status Code | Description | Common Causes |
|---|---|---|
400 | Bad Request | Invalid parameters, missing required fields |
401 | Unauthorized | Invalid API token or expired OAuth token |
403 | Forbidden | Insufficient permissions for the action |
404 | Not Found | Issue, project, or user not found |
Setup Guide
1
Generate API Token
Navigate to Atlassian Account Security and create a new API token.
2
Configure Integration
In Plura, add the Jira integration with your API token, email, and instance URL.
3
Test Connection
Create a test issue to verify authentication and permissions are configured correctly.
4
Add to Workflow
Use the API Call Node to integrate Jira actions into your AI agent workflows.
Best Practices
- Use Issue Keys: Always reference issues by their key (e.g.,
PROJ-123) for consistency - Validate Before Creation: Check for duplicate issues before creating new ones using search
- Add Context: Include relevant conversation context in issue descriptions and comments
- Set Priorities: Automatically set priorities based on conversation sentiment and urgency
- Track Updates: Use comments to maintain an audit trail of AI-driven updates
Next Steps
- API Call Node — Learn how to integrate Jira into workflows
- Decision Triggers — Route based on issue data
- Building Workflows — Create end-to-end integrations