The Jira integration allows you to create and track Jira issues directly from Intigriti submissions. By connecting your programs to Jira Cloud, you can streamline remediation workflows and ensure vulnerabilities are handled within your existing development processes.
🔓 Subscriptions: Starter, Core, Premium, Enterprise
Create a Jira connection
⚙️Roles: Company Admin
To use Jira with your programs, you first need to create a Jira connection at company level.
Go to Admin > Integrations > Jira Cloud.
Click Add connection.
Add a name and logo.
Insert your Jira URL: https://*.atlassian.net
Click Connect.
Authenticate with your Jira account and grant the required permissions.
Complete the setup.
The Jira connection is created once per company and can be reused across multiple programs.
Jira permissions
When authenticating Jira for use with Intigriti, we strongly recommend verifying permissions up front. Ensuring the correct permissions are in place helps prevent configuration issues later when setting up Jira integrations at program level.
If the Jira integration user lacks required permissions, you may encounter problems such as Jira projects or issue types not appearing in dropdowns, or priority and status mappings showing no available options during configuration.
To successfully configure and activate the Jira integration, make sure the Jira integration user has the following permissions.
Project permissions: Browse projects, View workflows in read-only mode
Issue permissions: Create issues, Edit issues, Transition issues, Resolve issues, Close issues, Delete issues (optional)
Comment permissions: Add comments
Attachment permissions: Create attachments
If these permissions are missing, the Jira project, issue types, priorities, or statuses may not be visible during configuration. For more information on managing Jira permissions, refer to Atlassian’s documentation.
Jira IP whitelisting
If your Jira instance uses IP whitelisting, you must allow traffic from Intigriti’s IP addresses before creating the Jira connection. This ensures that authentication and issue creation requests from the Intigriti platform are not blocked.
💡Note: We recommend completing IP whitelisting proactively before setting up the Jira connection. If you need the list of IP addresses to whitelist, contact our technical support team via the chat.
After completing IP whitelisting, some users may notice that the Jira integration does not activate immediately. This can happen if the existing connection needs to be refreshed on the platform side. To resolve this:
Go to Admin > More> Integrations.
Select Jira Cloud Integration.
Edit the desired Jira connection and re-enter your credentials or confirm the existing connection settings.
Save the changes and re-activate the integration.
Reactivating the integration in this way applies recent network changes and typically restores full functionality.
Configure Jira issues for a program
⚙️Roles: Company Admin, Program Admin
After the Jira connection is created, you can configure how submissions are pushed to Jira for a specific program.
Open a program and go to Integrations.
Select Jira Cloud and create a new integration.
Enter an integration name, for example the Jira project name, and add a logo.
Choose the Jira connection that can access the project.
Select the Jira project where issues should be created.
Select the Jira issue type that should be used for new submissions.
Choose if the issue needs to be created automatically and upon the occurence of which submission status change.
Configure the Jira issue details.
Click Activate to enable the integration.
When activation is successful, the integration becomes active immediately and issues can be created from submissions.
⚠️Beware: If the test issue creation fails, your configuration may not be compatible. Verify that the integration user has the necessary permissions and that the selected project, issue type, and field mappings are correct. If the issue persists, contact our technical support team via the chat.
Jira issue description template
You can include the default submission template in the Jira issue description. The template contains structured submission data to support remediation.
Submission references: code, URL, internal ref, internal link
Submission information: status & creation date
Researcher information: username & IP address
Report content: severity, domain, endpoint, type, PoC, impact, solution, Q&A, attachments
💡 Note: The following information is not included in the template: submission tags, custom fields, groups, assignee, and payouts.
Jira issue property configuration
Within the integration, you can configure how submission data maps to Jira issue fields.
Add up to 10 static Jira labels, for example the program name.
Map submission properties to Jira issue properties as needed, such as:
Severity to priority
Status to status
Closed reason to resolution
⚠️ Beware: If Jira issue fields can't be mapped to submissions properties, this is often caused by Jira configuration settings. Verify that the field is enabled for the selected issue type and that the issue type is correctly configured in your field configuration and screen schemes.
Indicate which submission messages should be added as Jira issue comments.
Choose whether the submission template in the issue description should stay synchronized after the Jira issue is created.
💡 Note: Custom Jira fields cannot be mapped directly within the Intigriti platform. If you need to populate custom fields, use Jira Automation rules, which is the recommended approach, or custom post-functions or scripts in your Jira workflow. These rules run after the issue is created and allow you to update fields based on predefined conditions. This configuration must be handled by your Jira administrator, as it is not managed or triggered from the Intigriti platform and is commonly required when custom fields are mandatory or part of internal Jira processes.
Best practices
Validate Jira permissions and field configurations before activating the integration to avoid missing projects, issue types, or mapping options during setup.
Use automatic issue creation only for submission states that are ready for remediation to prevent unnecessary or premature Jira tickets.
Keep Jira issue descriptions synchronized when development teams rely on up-to-date submission details for remediation.
Reconnect the program’s Jira integration after making changes to your Jira instance, even for small updates such as renaming issue types or priorities. This helps refresh the connection and ensures configuration changes are correctly applied to the integration.
Related articles