Jira Integration Setup Guide
This guide walks you through connecting Lathe Studio to your Jira Cloud instance.
Prerequisites#
- Jira Cloud account (Atlassian)
- Project admin access in Lathe Studio
- Jira project where you want to create issues
Connecting Jira#
Step 1: Initiate Connection
- Navigate to Project Settings → Jira
- Click "Connect Jira"
- You'll be redirected to Atlassian for authorization
Step 2: Authorize
- Log in to your Atlassian account (if not already logged in)
- Review the permissions requested:
- Read your Jira user information
- Read Jira project and issue data
- Create and modify issues in Jira
- Offline access (for refresh tokens)
- Click "Allow"
Step 3: Configure Project
After authorization, configure your Jira project settings:
- Jira Project Key: Enter your Jira project key (e.g., "PROJ", "ENG")
- Default Issue Type: Select the issue type for bugs (usually "Bug")
- Click "Save Configuration"
Field Mappings#
Control which Lathe Studio fields appear in Jira issues:
Available Fields
| PT Field | Jira Location | Description |
|---|---|---|
| Test Case Title | Issue Summary | Main identifier |
| Priority | Priority Field | P0-P3 mapping |
| Test Steps | Description | Formatted steps |
| Tester Notes | Description | Execution notes |
| Run Name | Description | Test run context |
| Build Name | Description | Build information |
| Environment | Description | Test environment |
Configure Mappings
- Go to Project Settings → Jira
- Scroll to Field Mappings section
- Toggle fields on/off as needed
- Changes apply to future bug pushes
Pushing Bugs to Jira#
From Test Execution
- Open a test run (submitted or completed status)
- Find a failed test case
- Click "Push to Jira"
- Review the bug details:
- Title: Auto-populated from test case
- Description: Includes steps, notes, environment info
- Attachments: Screenshots and files
- Click "Push to Jira" to create
Batch Push
- In a submitted/completed run, click "Submit Bugs" in header
- Modal shows all failed tests
- Review and select which to push
- Click "Push Selected" or "Push All"
After Pushing
- Jira issue key appears on the execution (e.g., "PROJ-123")
- Click the key to open in Jira
- Status syncs back to Lathe Studio (when configured)
Troubleshooting#
Connection Issues
"Could not connect to Jira"
- Verify you're using Jira Cloud (not Server/Data Center)
- Check internet connection
- Try reconnecting: Project Settings → Jira → Disconnect → Connect
"Invalid credentials"
- Ensure you authorized the correct Atlassian account
- Check that you have access to the Jira project
Push Issues
"Failed to create issue"
- Verify Jira project key is correct
- Check that you have "Create Issues" permission in Jira
- Review field mappings for required fields
"Attachments failed to upload"
- Max file size: 10MB per file
- Max 5 attachments per push
- Supported: PNG, JPG, GIF, PDF, TXT
Sync Issues
Issues not syncing status from Jira:
- Webhook may not be configured
- Contact your admin to verify webhook setup
Security & Permissions#
OAuth Scopes
Lathe Studio requests these Jira permissions:
read:jira-user: Verify your identityread:jira-work: Read project and issue datawrite:jira-work: Create and update issuesoffline_access: Refresh tokens automatically
Data Flow
- OAuth tokens stored encrypted in database
- No Jira credentials stored
- Direct API communication (Jira → PT)
- Webhooks for status updates (optional)
Unlinking Jira#
To disconnect:
- Go to Project Settings → Jira
- Click "Disconnect"
- Confirm disconnection
Note: Previously pushed issues remain linked. New pushes will not be possible until reconnected.
Advanced Configuration#
Priority Mapping
Map PT priorities to Jira priorities in Project Settings:
- P0 → Highest/High
- P1 → High/Medium
- P2 → Medium/Low
- P3 → Low/Lowest
Custom Fields
To include custom Jira fields:
- Contact your admin
- Configure in Jira project settings
- Map in Lathe Studio field mappings
For additional help, contact support.