How It Works
The Jira integration is configured at the program level. You supply your Jira instance URL and the target project details, and Hackrate stores those alongside your program. When an admin clicks to create a ticket, Hackrate uses those stored settings to open a pre-filled ticket in the correct Jira project.The Jira integration is configured by an admin in program settings. Only one Jira project can be connected to a program at a time. If you need to route tickets to different projects depending on the type of finding, consider using multiple programs or routing rules in Jira itself.
Configuring the Jira Integration
1
Open Program Settings
Go to your program in Hackrate and open Settings. You need a SuperAdmin or StandardAdmin role on the program to configure integrations.
2
Navigate to the Jira section
In the Integrations tab, find the Jira card.
3
Enter your Jira Base URL
Provide the base URL of your Jira instance. For Jira Cloud this looks like
https://your-company.atlassian.net. For Jira Server or Data Center, use the URL your team navigates to when opening Jira.4
Enter the Project ID
Supply the numeric ID of the Jira project where security tickets should be created. You can find this in your Jira project settings.
5
Enter the Issue Type ID
Provide the Issue Type ID for the kind of ticket you want to create — for example, the ID for “Bug” or “Security Vulnerability” in your project’s issue type scheme.
6
Save the configuration
Click Save. The Jira integration is now active for this program. The Jira details will appear in the report management sidebar for every report in the program.
Creating a Jira Ticket from a Report
1
Open a report
Go to Reports → Manage and open any report within the program that has Jira configured.
2
Find the Jira section
In the report management view, a Jira panel shows your configured base URL, project, and issue type. This confirms the integration is active.
3
Create the ticket
Click Create Jira Ticket. Hackrate pre-fills the ticket with the report title, a description derived from the report content, the severity level, and a link back to the Hackrate report. Review and adjust the content if needed, then submit.
4
Track in Jira
The ticket appears in your Jira project board. Your engineering team can pick it up from their normal Jira workflow. The Hackrate report retains a reference to the Jira ticket for traceability.
What Data Is Sent to Jira
When you create a ticket from a report, the following information is included:Report Title
The vulnerability title from Hackrate becomes the Jira ticket summary.
Severity
The Hackrate severity level (Critical, High, Medium, Low) is included in the ticket body to help engineers prioritize.
Description
The report’s description, impact statement, and reproduction steps are included so engineers have the full context without needing Hackrate access.
Hackrate Link
A direct link back to the Hackrate report is embedded in the ticket so reviewers can navigate between systems easily.
Tips for Getting the Most Out of the Integration
Finding your Jira Project ID
Finding your Jira Project ID
In Jira Cloud, go to your project, open Project Settings → Details, and look for the Project ID in the URL or the settings fields. In Jira Server, the Project ID is shown in Project Settings → Edit Project.
Finding your Jira Issue Type ID
Finding your Jira Issue Type ID
In Jira Cloud, go to Project Settings → Issue Types, click the issue type you want to use, and note the numeric ID in the URL. In Jira Server, you can find issue type IDs under Jira Administration → Issues → Issue Types.
Routing tickets to different projects by severity
Routing tickets to different projects by severity
If your engineering workflow requires Critical and High findings in one project and Medium and Low in another, you can configure two separate Hackrate programs with different Jira settings, or handle routing automatically with Jira Automation rules that re-assign issues based on labels or custom fields you populate.