Jira Integration Setup Guide

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

  1. Navigate to Project Settings → Jira
  2. Click "Connect Jira"
  3. You'll be redirected to Atlassian for authorization

Step 2: Authorize

  1. Log in to your Atlassian account (if not already logged in)
  2. 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)
  3. Click "Allow"

Step 3: Configure Project

After authorization, configure your Jira project settings:

  1. Jira Project Key: Enter your Jira project key (e.g., "PROJ", "ENG")
  2. Default Issue Type: Select the issue type for bugs (usually "Bug")
  3. Click "Save Configuration"

Field Mappings#

Control which Lathe Studio fields appear in Jira issues:

Available Fields

PT FieldJira LocationDescription
Test Case TitleIssue SummaryMain identifier
PriorityPriority FieldP0-P3 mapping
Test StepsDescriptionFormatted steps
Tester NotesDescriptionExecution notes
Run NameDescriptionTest run context
Build NameDescriptionBuild information
EnvironmentDescriptionTest environment

Configure Mappings

  1. Go to Project Settings → Jira
  2. Scroll to Field Mappings section
  3. Toggle fields on/off as needed
  4. Changes apply to future bug pushes

Pushing Bugs to Jira#

From Test Execution

  1. Open a test run (submitted or completed status)
  2. Find a failed test case
  3. Click "Push to Jira"
  4. Review the bug details:
    • Title: Auto-populated from test case
    • Description: Includes steps, notes, environment info
    • Attachments: Screenshots and files
  5. Click "Push to Jira" to create

Batch Push

  1. In a submitted/completed run, click "Submit Bugs" in header
  2. Modal shows all failed tests
  3. Review and select which to push
  4. 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 identity
  • read:jira-work: Read project and issue data
  • write:jira-work: Create and update issues
  • offline_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:

  1. Go to Project Settings → Jira
  2. Click "Disconnect"
  3. 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:

  1. Contact your admin
  2. Configure in Jira project settings
  3. Map in Lathe Studio field mappings

For additional help, contact support.