Set up an integration to push Cobalt findings to Jira.

Set up an integration to push Cobalt findings to Jira.


:::info
Synchronize Cobalt pentest [findings](https://docs.cobalt.io/en-us/articles/findings-6prkG67iav) with Jira issues bi-directionally. The availability of this feature depends on your [PtaaS tier](https://docs.cobalt.io/en-us/articles/cobalt-ptaas-tiers-tGUEyGwLaS).

To sync DAST & Engagement findings, use the [Integration Builder](https://docs.cobalt.io/en-us/articles/integration-builder-Aelp0wU7EI).

:::

## **Overview**

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 integrate Jira with Cobalt to streamline your workflows. With this integration, you can:

* **Push Cobalt pentest findings as issues** to your Jira project.
  * The [auto-push](https://docs.cobalt.io/en-us/articles/push-cobalt-findings-to-jira-cdNUJlnblj#h-how-auto-push-works) option allows you to push findings to Jira automatically.
  * Pentest collaborators can also [push findings manually](https://docs.cobalt.io/en-us/articles/push-cobalt-findings-to-jira-cdNUJlnblj#h-push-findings-manually)—if they’re not already synchronized.
* **Synchronize the status of Jira issues with Cobalt findings** once your team has completed remediation.

The integration works through **Cobalt plugins for Jira** available on the Atlassian Marketplace.

| **Jira Setup** | **Cobalt Plugin for Jira** | **Configuration Guide** |
|----|----|----|
| Jira Cloud | [Cobalt for Jira Cloud](https://marketplace.atlassian.com/apps/1222623/cobalt-for-jira-cloud) | [Jira Cloud Integration](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo) |
| Jira Data Center | [Cobalt for Jira DC](https://marketplace.atlassian.com/apps/1224424/cobalt-for-jira-dc-server) | [Jira Data Center Integration](https://docs.cobalt.io/en-us/articles/jira-data-center-integration-WzRSMUJ1U7) |

If you have problems with your integration, see our [troubleshooting guide](https://docs.cobalt.io/en-us/articles/troubleshoot-your-jira-integration-air4lSUkWG). To get more help, please contact your Customer Success Manager.

## **Frequently Asked Questions**


### What is a finding?

A finding is a vulnerability that a pentester reports during a pentest on the Cobalt platform. Learn more about [findings](https://docs.cobalt.io/en-us/articles/findings-6prkG67iav).

### What is a Jira issue (ticket)?

In Jira, an issue is a work item or an event that needs to be investigated within a project. Issues may also be referred to as tickets.

In the context of Jira integrations, a ticket is a finding that was synchronized with Jira.

### Which required fields are supported to create Jira issues?

The following fields are required to create a Jira issue:

* Summary
* Issue type
* Reporter

### Does the integration support custom required fields?

No, custom required fields are not supported.

### Does the integration support the Component field on Jira issues?

No, components are not supported. Learn more about [Jira project components](https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/).

### What types of Jira projects does the integration support?

The integration supports software development Jira projects, such as:

* Kanban
* Scrum
* Bug Tracking

### How often findings are synchronized between Cobalt and Jira?

Findings are synchronized frequently between the Cobalt platform and Jira, usually every minute.

### Will historical findings be synchronized after I configure the Jira integration for a pentest?

Yes, only if findings are in the Pending Fix state.

### Can I set up the Jira integration if I sign in using single sign-on (SSO)?

You can set up the integration regardless of your [sign-in method](https://docs.cobalt.io/en-us/articles/sign-in-to-cobalt-EGTXEey2h8#h-sign-in-methods) and [two-factor authentication](https://docs.cobalt.io/en-us/articles/sign-in-to-cobalt-EGTXEey2h8#h-two-factor-authentication) status.


:::info
**Jira Plugins SLA**

Cobalt provides the Jira plugins to their customers to facilitate delivery of its services. Cobalt provides this integration on an “as-is” basis, and makes no guarantees on its functionality or interoperability with customers’ systems.

Customers requiring support for the plugins should contact their Customer Success Manager. All requests are addressed within three (3) business days.

:::




Integrate Jira with Cobalt

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

Push Cobalt Findings to Jira

Jira Cloud Integration

Jira Data Center Integration

Troubleshoot Your Jira Integration

Switching to a New Jira Instance

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

Integrate Jira with Cobalt

Share

Jira Cloud Integration

Jira Data Center Integration

Push Cobalt Findings to Jira

Synchronize Cobalt Severity Levels with Jira

Switching to a New Jira Instance

Troubleshoot Your Jira Integration

Share

Integrate Jira with Cobalt

Share

Jira Cloud Integration

Jira Data Center Integration

Push Cobalt Findings to Jira

Synchronize Cobalt Severity Levels with Jira

Switching to a New Jira Instance

Troubleshoot Your Jira Integration

Share