Skip to main content
The Jira integration enables your team to create Jira tickets directly from LaunchSafe findings, ensuring vulnerabilities flow into your existing issue tracking and sprint planning workflow.

Prerequisites

  • A Jira Cloud instance (Jira Server/Data Center is not currently supported)
  • Admin or project admin access to the Jira project where tickets should be created
  • An active LaunchSafe workspace

Setup

1

Navigate to Integrations

In the LaunchSafe dashboard, go to Integrations in the sidebar and locate the Jira card.
2

Connect Jira

Click Connect Jira. You’ll be redirected to Atlassian’s OAuth authorization page.
3

Authorize LaunchSafe

Log in with your Atlassian account and grant LaunchSafe access. The following permissions are requested:
PermissionPurpose
Read Jira projectsList available projects for ticket creation
Create issuesCreate new tickets from findings
Add attachmentsAttach evidence screenshots and proof-of-concept data
Read issue typesMap to your project’s issue types (Bug, Task, Story)
4

Configure project mapping

Select the default Jira project where tickets should be created. You can also configure:
  • Issue type — Bug (recommended), Task, or Story
  • Priority mapping — how LaunchSafe severity maps to Jira priority
  • Labels — automatically applied labels (e.g., security, launchsafe)
  • Assignee — default assignee for new tickets (optional)

Creating tickets from findings

From any finding in LaunchSafe:
  1. Click the Create Jira Ticket button on the finding detail page
  2. Review the pre-populated fields (you can edit before creating)
  3. Click Create — the ticket is created in your Jira project
  4. A link to the Jira ticket appears on the finding for tracking

Field mapping

LaunchSafe populates Jira tickets with structured information from the finding:
LaunchSafe fieldJira fieldContent
TitleSummaryVulnerability title with CWE reference
SeverityPriorityMapped via your configured priority mapping
DescriptionDescriptionFull finding details in Jira markup format
EvidenceDescription (appended)HTTP request/response, code snippets, data flow
CategoryLabelsVulnerability category (e.g., sql-injection, xss)
CVSS ScoreCustom field (if configured)Numeric CVSS v3.1 score
RemediationDescription (appended)Step-by-step fix instructions with code examples
LaunchSafe URLDescription (link)Direct link back to the finding in LaunchSafe

Priority mapping

The default priority mapping follows industry-standard severity-to-priority translation:
LaunchSafe severityJira priority
CriticalHighest
HighHigh
MediumMedium
LowLow
InfoLowest
You can customize this mapping in IntegrationsJiraSettings.

Bulk ticket creation

For scans with many findings, you can create tickets in bulk:
  1. Go to the Findings page
  2. Use severity filters to select the findings you want to ticket
  3. Click Create Jira Tickets (bulk action)
  4. Review and confirm — tickets are created for all selected findings

Duplicate prevention

LaunchSafe tracks which findings have associated Jira tickets. If you attempt to create a ticket for a finding that already has one, you’ll be warned and shown the existing ticket link. This prevents duplicate tickets from cluttering your backlog.

Disconnecting

To disconnect Jira, go to IntegrationsJiraDisconnect. Existing Jira tickets created by LaunchSafe are not affected — they remain in your Jira project.