SpartanX integrates directly with Jira, enabling security teams to push vulnerability findings as Jira tickets automatically. This connection eliminates manual handoffs between security assessments and developer remediation workflows.
Connecting Jira via OAuth
To set up the integration, navigate to Data Integrations in the left-hand navigation and click Integrations. Scroll to the Project Management section and select Jira. Click Connect to begin an OAuth authentication flow using your Atlassian account credentials.
Review and accept the authorization request to grant SpartanX the necessary permissions. You will then be prompted to select your Jira workspace and complete the setup. Once confirmed, the Jira integration is active and ready to use.
Option 1: Creating Tickets Per Vulnerability via Actions
The first method allows you to create Jira tickets for individual vulnerabilities directly from the Vulnerabilities view. Navigate to Vulnerabilities, select a collection, and optionally apply filters to narrow your results. For example, you could filter by vulnerability type to group findings assigned to the same development team.
Select one or more vulnerabilities from the list, click Actions, and choose Create Jira Issue. SpartanX will generate a Jira ticket for each selected vulnerability and route it to your default Jira project space.
Option 2: Bulk Ticket Generation via Runbook
For large-scale ticket creation, use the Runbook feature. From the Vulnerabilities section, click Runbook and select Jira. You can configure the following options:
Collection: Choose the collection you want to generate tickets from, such as a perimeter scan or specific application environment.
Assets: Select specific assets within the chosen collection.
Severity Threshold: Set the minimum severity level for ticket creation. Selecting Low generates tickets for Low, Medium, High, and Critical findings. Selecting High includes only High and Critical.
Jira Project Key: Specify the destination Jira project space. This allows you to route tickets to different teams rather than always using the default space.
Epic Key (optional): Link all generated tickets to an existing Jira epic.
Issue Type: Set the ticket type to match your team's workflow, such as Bug, Task, or Improvement. The appropriate type varies by organization.
Once you have completed the configuration, run the task. SpartanX launches a playbook that connects to the Jira MCP server and generates all tickets automatically. You will receive a notification when the process is complete.
Conclusion
The Jira integration in SpartanX bridges the gap between security findings and developer workflows. Whether you prefer creating tickets one at a time from the Vulnerabilities view or generating them in bulk through a runbook, the integration scales to fit organizations of any size and keeps remediation tracking tightly coupled to the vulnerability data in SpartanX.