Jira Integration

Overview

Connect Solatis with Jira to automatically create tickets from meetings, link documentation to issues, and streamline project management workflows.

Setup

Connect Jira

Step 1: Authorize

1. Integrations → Jira
2. Click "Connect Jira"
3. Select Jira site
4. Grant permissions
5. Authorize access

Required Permissions:

• Read/write issues
• Read projects
• Read users
• Write comments
• Manage workflows

Step 2: Configuration

Jira Site: yourcompany.atlassian.net
Default Project: PROJ
Default Issue Type: Task
Default Priority: Medium

Features

Automatic Ticket Creation

From Meetings:

Meeting: Product Planning
Action Item detected: "Update API documentation by Nov 15 - @alice"

Auto-creates:
PROJ-123: Update API documentation
- Type: Task
- Assignee: Alice Chen
- Due Date: Nov 15, 2024
- Description: From Product Planning meeting on Oct 11
- Link: Meeting transcript

From Documents:

Document analysis finds: "TODO: Fix authentication bug"

Auto-creates:
PROJ-124: Fix authentication bug
- Type: Bug
- Priority: Medium
- Labels: technical-debt, security
- Link: Source document

Bidirectional Sync

Solatis → Jira:

• Create issues
• Update status
• Add comments
• Attach documents
• Link meetings

Jira → Solatis:

• Import existing issues
• Status updates
• Comment sync
• Attachment linking
• Relationship tracking

Smart Field Mapping

Automatic Mapping:

Action Item Detection:
"Alice needs to fix the login bug by Friday, high priority"

Mapped to Jira:
- Summary: "Fix login bug"
- Assignee: Alice Chen (looked up)
- Due Date: Next Friday
- Priority: High
- Type: Bug (detected from "bug")
- Labels: login, authentication (extracted)

Custom Mapping: Configure how Solatis fields map to Jira:

Solatis Priority → Jira Priority
- Urgent → Highest
- High → High
- Medium → Medium
- Low → Low

Solatis Type → Jira Issue Type
- Bug Report → Bug
- Feature Request → Story
- Task → Task
- Question → Task

Advanced Features

Issue Templates

Create Reusable Templates:

Bug Template:

type: Bug
priority: Medium
labels: [bug, needs-triage]
fields:
  - name: Environment
    required: true
  - name: Steps to Reproduce
    required: true
  - name: Expected Behavior
    required: true
  - name: Actual Behavior
    required: true

Feature Template:

type: Story
priority: Medium
labels: [feature-request]
fields:
  - name: User Story
    required: true
  - name: Acceptance Criteria
    required: true
  - name: Design Mockups
    required: false

Workflow Automation

Example: Meeting → Jira Flow

Meeting ends
  ↓
AI extracts action items
  ↓
For each action item:
  - Create Jira ticket
  - Set assignee (from mention)
  - Set due date (from context)
  - Add meeting link
  - Set appropriate labels
  ↓
Notify assignees
  ↓
Update project board

Link Management

Automatic Linking:

• Meeting transcripts linked to tickets
• Documents linked to related issues
• Conversations linked to epics
• Cross-reference detection

Example:

Jira: PROJ-123 (Update docs)
↓
Linked in Solatis:
- Meeting where discussed (Oct 11)
- Related document (API Docs v2)
- Chat conversation about it
- Similar past tickets

Comment Synchronization

Two-Way Comments:

Solatis → Jira:

AI Summary comment in Solatis:
"Meeting concluded API v2 specs are 80% complete"

Appears in Jira:
[Solatis Bot] Meeting Update:
API v2 specs are 80% complete
Source: Product Planning Meeting (Oct 11)

Jira → Solatis:

Developer comment in Jira:
"Fixed the bug, PR #234 ready for review"

Appears in Solatis:
Ticket update notification
+ link to Jira comment

Configuration

Project Settings

Default Project Configuration:

Project: PROD
Issue Types:
  - Task (default)
  - Bug
  - Story
  - Epic

Priorities:
  - Highest
  - High
  - Medium (default)
  - Low
  - Lowest

Workflow States:
  - To Do
  - In Progress
  - In Review
  - Done

Assignee Mapping

User Mapping:

Solatis User → Jira User
alice@company.com → alice.chen
john@company.com → john.smith
sarah@company.com → sarah.johnson

Auto-mapping rules:
- Match by email
- Match by name
- Fallback to unassigned

Label Management

Auto-Labeling:

Keywords → Labels
"bug" → bug
"security" → security
"api" → api
"urgent" → urgent
"customer-facing" → customer-impact

Meeting Types → Labels
Product Planning → product
Engineering Sync → engineering
Customer Call → customer

Use Cases

Sprint Planning

Workflow:

1. Weekly planning meeting
   ↓
2. Discuss stories and priorities
   ↓
3. Solatis captures decisions
   ↓
4. Auto-creates/updates tickets
   ↓
5. Tickets added to sprint
   ↓
6. Team notified

Bug Triage

Workflow:

1. Customer reports bug via support
   ↓
2. Logged in support system
   ↓
3. Solatis analyzes report
   ↓
4. Creates Jira bug ticket:
   - Severity assessed
   - Component identified
   - Engineer assigned
   ↓
5. Bug enters workflow

Feature Requests

Workflow:

1. Feature requested in meeting
   ↓
2. Discussion captured
   ↓
3. AI extracts requirements
   ↓
4. Creates Jira story:
   - User story format
   - Acceptance criteria
   - Linked to discussion
   ↓
5. Product team reviews

Best Practices

Ticket Quality

Do:

• ✅ Clear, actionable titles
• ✅ Sufficient context
• ✅ Proper categorization
• ✅ Realistic estimates
• ✅ Link to sources

Don't:

• ❌ Vague descriptions
• ❌ Missing acceptance criteria
• ❌ Wrong issue type
• ❌ Duplicate tickets
• ❌ Orphaned tickets

Integration Hygiene

Regular Maintenance:

• Review auto-created tickets weekly
• Merge duplicates
• Update stale tickets
• Clean up old labels
• Archive completed projects

Permission Management

Security:

• Least privilege access
• Regular audits
• Remove unused integrations
• Monitor API usage
• Rotate credentials quarterly

Troubleshooting

Tickets Not Creating:

• Verify Jira connection active
• Check project permissions
• Ensure issue type exists
• Try manual creation test
• Review error logs

Wrong Assignees:

• Check user mapping
• Verify Jira permissions
• Update mapping rules
• Test with known users
• Fallback to unassigned if needed

Missing Links:

• Verify link permissions
• Check issue key format
• Ensure both systems accessible
• Try manual link first
• Contact support

Advanced Scenarios

Epic Management

Auto-Epic Creation:

Quarterly planning meeting
  ↓
Major initiatives identified
  ↓
Create epics for each:
- Q4 API v2 Development
- Q4 Mobile App Redesign
- Q4 Performance Optimization
  ↓
Link related tickets to epics

Dependency Tracking

Automatic Detection:

Meeting: "We can't start testing until specs are done"

Creates dependency:
PROJ-124 (Testing) blocks on PROJ-123 (Specs)

Status Workflows

Custom Workflows:

To Do → In Progress → Code Review → QA → Done

Automated transitions:
- PR created → Code Review
- PR approved → QA
- QA passed → Done

Next Steps

• Asana Integration - Alternative PM tool
• Task Automation - Workflow automation
• Business Intelligence - Ticket analytics

---

Need help? Email integrations@solatis.team

Last Updated: October 11, 2025