Streamline your remediation workflows with the Jira integration.

Streamline your remediation workflows with the Jira integration.


:::info
Learn how auto-push works and how to push findings to Jira manually.

:::

## **How Auto-Push Works**

Once an [Organization Owner](https://docs.cobalt.io/en-us/articles/user-roles-and-permissions-oCij6uRrUR#h-organization-owner) or [Member](https://docs.cobalt.io/en-us/articles/user-roles-and-permissions-oCij6uRrUR#h-organization-member) has enabled the Jira integration on a pentest, findings start to automatically synchronize with the selected Jira project. The **Auto-Push** option is enabled by default.

Here’s how auto-push works:

* When a new finding in the **Pending Fix** state is created on a pentest in Cobalt, a new issue is created in your Jira project.
  * The issue status in Jira is based on the project configuration. It’s the first status in your project workflow, for example, To Do.
  * If the integration is enabled on a pentest with existing findings, Jira tickets are created for them retroactively.
* Findings whose [state](https://docs.cobalt.io/en-us/articles/finding-states-De6IE4W5Zw) is not Pending Fix are not automatically pushed to Jira. If the finding state changes to Pending Fix, the finding is automatically pushed.
* Once an issue is created in Jira, the issue ID appears on the finding in Cobalt under **External Issue Tracking**. Click the link to navigate to the issue.

 ![](https://brainfish-storage-prod.s3-accelerate.amazonaws.com/uploads/e1eb5d82-35e0-4c9f-bde1-0baec07941c1/72930f0c-d3e8-43e9-8c6c-26bf97d29a2c/image.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAUPPN5IL36DGGCY5R%2F20260425%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20260425T140132Z&X-Amz-Expires=3000&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEMn%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMiJIMEYCIQCCnlN6BdSGOGeJURt%2FBcTzsN6WRSZGEnQLsqvSlBxGaQIhANK8NeLXFRHUtuW%2FO2TeFjrTMyJqjGE%2Bq7pQmUSWroIJKuYFCJL%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEQAhoMMzA4MTI1OTc1Mjg3Igwhkw%2FL4xY8oHk5wKoqugVeSI1H0jYEjx%2BSQ7D5ihTPUFwd77JWsenSlLxCQWyzkEjOoez1LoLQldnHk%2B%2F9NmvABV0LTkIjszKLZGiEWl8r%2FF9siwlf102qfAz0oApH3O5sgi8Bn8k1A8gjGrypEZnCdqTDWzSG2U5Zyn1Bu0Po1QHu42bWksg67fSw9zkQKEw7sI127iM0u8%2FOtvhxGoYnCrNYVKWGh0k3TFIkDOUAXaP75SNcOf%2FttShU38yKECnb2vbiabpdNHYZ3O6lpiEHTRlGxahD9EwyfFDXlXOWQmg5jFUJOyMAY9KsTbKlKAzPaIcLjmELXazI3mbyeoTj0hNAnCbwRl4xgLxMcHlg6pNeKk4Gprz96CgnQ5BsX7UQmOCSOSgtFjr%2FR5UbGb5F11GGoq9ihxTsAlLQYzItFeYwPkQWws8lOz2IgIe7nDj0YydQLms6Bu6qTgwklN%2B3aWg3sf%2BoYCTsrLkebu1AhI21U5w6xxfYq%2FXCDTmoJ%2FcdK9myA2j8iAej0ptYDn%2BcDJNtGxUEME%2BnIeHQ1adLnXTV2UEkdIO%2FjAWBwCxyLtYKv6zjIqhUy4qgsIsrvoSDAImz4gOvixBfPXjoV7RTs9cBxY2oyfYaP9oDxjjVOYYX75q8InzhKAQ9yjusid7MoeQVyVzZ5rypWjLDGsWVwAyZyrTsHlSw13J5bjtJqGww6BrwRnTNNsuRV6UaFiBeGeqXRmXeoqjFWblv7Ek82yIqRxqVHufrghcR1PpItVdZiHzQP3UI7cy0SZw08ncVGCE6OCSpKe95Lx5lTHPybopY%2FS0F2b%2FXdYgpZtww2tSiWv7dqrTlzraJwwWcU5IGkTuvHaXXy%2B%2Fz9XFsYZHW3xPYoi0tmA%2BGFK2BCPhAt6P%2BhEIDP%2BKyLdf4V4jLMwxDD9%2BOe4mTaITsWONDaFGGGcYwbxF4tOToazDt%2F7HPBjqPAX7jTtmWJtBaSrl5%2BESw1VM0FEA58a5oi6orA6yZCh8xVa4CaD6vnOAJNdLDT%2FiIJZgpgRQNLNXsIj2voOwr9nZK%2FU19gfTOPuPghBFISlMtHSB1jZCzIO8%2BXuKbgD2DpcXIrN5rWTFIoW56bFz8nH%2F%2F1i7uNUaebb5hjKJG8Q5T6cfiyNorT59rKY5nkosq&X-Amz-Signature=8183ce32bb960f84f24d93fb454e29b066a215d0b4028eeeb4392b20046babdb&X-Amz-SignedHeaders=host&response-content-disposition=attachment)

## **Turn Auto-Push on or Off**

As an [Organization Owner](https://docs.cobalt.io/en-us/articles/user-roles-and-permissions-oCij6uRrUR#h-organization-owner) or [Member](https://docs.cobalt.io/en-us/articles/user-roles-and-permissions-oCij6uRrUR#h-organization-member), you can turn auto-push on or off for specific pentests as needed.


1. In Cobalt, go to **Integrations** > **Jira** > **Configuration**.
2. For the desired pentest, turn the **Auto-Push** toggle on or off.

 ![](https://brainfish-storage-prod.s3-accelerate.amazonaws.com/uploads/e1eb5d82-35e0-4c9f-bde1-0baec07941c1/1fd6df06-d0b5-4ee9-9a45-a504aa109249/image.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAUPPN5IL36DGGCY5R%2F20260425%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20260425T140132Z&X-Amz-Expires=3000&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEMn%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMiJIMEYCIQCCnlN6BdSGOGeJURt%2FBcTzsN6WRSZGEnQLsqvSlBxGaQIhANK8NeLXFRHUtuW%2FO2TeFjrTMyJqjGE%2Bq7pQmUSWroIJKuYFCJL%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEQAhoMMzA4MTI1OTc1Mjg3Igwhkw%2FL4xY8oHk5wKoqugVeSI1H0jYEjx%2BSQ7D5ihTPUFwd77JWsenSlLxCQWyzkEjOoez1LoLQldnHk%2B%2F9NmvABV0LTkIjszKLZGiEWl8r%2FF9siwlf102qfAz0oApH3O5sgi8Bn8k1A8gjGrypEZnCdqTDWzSG2U5Zyn1Bu0Po1QHu42bWksg67fSw9zkQKEw7sI127iM0u8%2FOtvhxGoYnCrNYVKWGh0k3TFIkDOUAXaP75SNcOf%2FttShU38yKECnb2vbiabpdNHYZ3O6lpiEHTRlGxahD9EwyfFDXlXOWQmg5jFUJOyMAY9KsTbKlKAzPaIcLjmELXazI3mbyeoTj0hNAnCbwRl4xgLxMcHlg6pNeKk4Gprz96CgnQ5BsX7UQmOCSOSgtFjr%2FR5UbGb5F11GGoq9ihxTsAlLQYzItFeYwPkQWws8lOz2IgIe7nDj0YydQLms6Bu6qTgwklN%2B3aWg3sf%2BoYCTsrLkebu1AhI21U5w6xxfYq%2FXCDTmoJ%2FcdK9myA2j8iAej0ptYDn%2BcDJNtGxUEME%2BnIeHQ1adLnXTV2UEkdIO%2FjAWBwCxyLtYKv6zjIqhUy4qgsIsrvoSDAImz4gOvixBfPXjoV7RTs9cBxY2oyfYaP9oDxjjVOYYX75q8InzhKAQ9yjusid7MoeQVyVzZ5rypWjLDGsWVwAyZyrTsHlSw13J5bjtJqGww6BrwRnTNNsuRV6UaFiBeGeqXRmXeoqjFWblv7Ek82yIqRxqVHufrghcR1PpItVdZiHzQP3UI7cy0SZw08ncVGCE6OCSpKe95Lx5lTHPybopY%2FS0F2b%2FXdYgpZtww2tSiWv7dqrTlzraJwwWcU5IGkTuvHaXXy%2B%2Fz9XFsYZHW3xPYoi0tmA%2BGFK2BCPhAt6P%2BhEIDP%2BKyLdf4V4jLMwxDD9%2BOe4mTaITsWONDaFGGGcYwbxF4tOToazDt%2F7HPBjqPAX7jTtmWJtBaSrl5%2BESw1VM0FEA58a5oi6orA6yZCh8xVa4CaD6vnOAJNdLDT%2FiIJZgpgRQNLNXsIj2voOwr9nZK%2FU19gfTOPuPghBFISlMtHSB1jZCzIO8%2BXuKbgD2DpcXIrN5rWTFIoW56bFz8nH%2F%2F1i7uNUaebb5hjKJG8Q5T6cfiyNorT59rKY5nkosq&X-Amz-Signature=e97522a002af7eaec26d3fdb7cfcf5c0eafe869a07bd06adf36204553c032dd3&X-Amz-SignedHeaders=host&response-content-disposition=attachment)

When auto-push is turned off, Jira issue statuses are still synchronized with Cobalt finding states.

## **Push Findings Manually**

As a [Pentest Team Member](https://docs.cobalt.io/en-us/articles/user-roles-and-permissions-oCij6uRrUR#h-pentest-team-member), you can push findings to Jira manually—if they’re not already synchronized. This may be needed if:

* [Auto-push](https://docs.cobalt.io/en-us/articles/push-cobalt-findings-to-jira-cdNUJlnblj#h-how-auto-push-works) is turned off on a pentest; or
* The [finding state](https://docs.cobalt.io/en-us/articles/finding-states-De6IE4W5Zw) is other than Pending Fix, even though auto-push is enabled. If you want to push findings in other states, you can do it manually.

To push a finding to Jira manually:


1. On the pentest page, navigate to the **Findings** tab, and select the desired finding.
2. Select **External Issue Tracking**, then select **Create issue in JIRA**.




Push Cobalt Findings to Jira

Cobalt Integrations Overview

Troubleshooting

HTTP Connector

Import Assets from Google Sheets

Map Cobalt Pentest Finding Severity to Jira Issue Priority

Modify Jira Issue Summary to contain Pentest Title

Create Azure DevOps Work Item for Findings

Send MS Teams notifications for Findings

Create GitLab tickets for Findings

Create Jira tickets for Findings

Send email notifications for Findings from Outlook

Create GitHub tickets for Findings

How to Guides

Connect your applications

Integration Builder

Synchronize Cobalt Severity Levels with Jira

Jira Cloud Integration

Jira Data Center Integration

Troubleshoot Your Jira Integration

Switching to a New Jira Instance

Integrate Jira with Cobalt

Slack

Microsoft Teams

Webhooks

DefectDojo

Kenna Security

Vanta

Carried Over Findings

Create Test Finding

Integrations

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

Pentests

Overview

Asset Details

Pentest Details

Scope & Test Period

Preparation

Create a Pentest

Pentest Process

Pentest States

Coverage Checklist

Pentest Expectations

Set Up an In-House Pentest

Complete an In-House Pentest (For Pentesters)

In House Pentests

Finding States

Severity Levels

Remediate Findings

Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

Insights

Planning

Cobalt Methodologies Overview

Web Methodologies

API Methodologies

External Network Methodologies

Internal Network Methodologies

Mobile Methodologies

Cloud Configuration Review Methodologies

Cloud Pentest Methodology

Desktop Methodologies

AI/LLM Methodologies

Digital Risk Assessment Methodology

Secure Code Review Methodologies

Methodologies

Attack Surface Monitoring (ASM)

Attack Surface

DAST Scanner Overview

Best Practices

Partial Scans: Reduced Scope

Scans

Sequence recorder

Targets

Target Authentication

Extra Hosts

Blackout Period

DAST Scanner

Account Overview

Account Settings

Password Best Practices

Sign In to Cobalt

Troubleshoot Sign-in Issues

User Account

Collaboration Overview

Collaborate on Pentests

Groups

Manage Pentest Collaborators

Manage Notifications

User Roles and Permissions

Collaboration

Organization Overview

Manage Users

Your Cobalt Contract

Configure SAML SSO

How to Configure SAML 2.0 for Cobalt 

SAML Migration: Update Your Configuration

SCIM Provisioning Setup Guide

Configure Organization Settings

Organization

Track Your Credits

Cobalt Credits

Cobalt PtaaS Tiers

Credits

Cobalt API Overview

Create a Personal Cobalt API Token

Get an Organization Token

Revoke Your Personal Cobalt API Tokens

Create or Modify an Asset

Import Findings to Google Sheets

Cobalt API

Glossary

March 2026

February 2026

January 2026

November 2025 

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

January 2025

December 2024

November 2024

October 2024

September 2024

August 2024

July 2024

June 2024

May 2024

April 2024

March 2024

January 2024

What's New

Guide

Cobalt Product Documentation

Push Cobalt Findings to Jira

Share

Share

Push Cobalt Findings to Jira

Share

Share