Learn how to reconfigure your Jira integration with Cobalt.

Learn how to reconfigure your Jira integration with Cobalt.


:::info
Learn how to reconfigure your Jira integration if you:

* Migrate from Jira Data Center (DC) to Jira Cloud
* Switch to a new Jira Cloud instance

:::

## **Migrating from Jira DC to Jira Cloud**

If you’re migrating entirely from Jira DC to Jira Cloud, do the following:


1. Uninstall the Cobalt Jira plugin from your Jira DC.
2. In Cobalt, delete the integration. Navigate to **Integrations** > **Jira**, and select **Delete**.

 ![](https://brainfish-storage-prod.s3-accelerate.amazonaws.com/uploads/e1eb5d82-35e0-4c9f-bde1-0baec07941c1/cc69b771-5af6-4344-a6fb-3b05b1e11650/image.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAUPPN5IL3UTWIVDH3%2F20260423%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20260423T193337Z&X-Amz-Expires=3000&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEKD%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMiJIMEYCIQCHiyYdzjPYCmgRJakZ7t1BsVOwVyiS6a9hHljm4EwdjwIhANkxQXjn9SS%2BiFFA8QG95FlwGKvquxrh9FpO%2FkXQE0HOKtsFCGkQAhoMMzA4MTI1OTc1Mjg3IgxSZZaS4pHwvTSErdEquAVttgwjcEf2f5uJmVcr%2BzhMNbK3W%2FknTIOIvPI%2B6FX7W7BYq9trpYIC9k%2Fum9y%2FPZUbfhFiKhZNCA6DEmGMLIs3PHxUbtkEQWDGBB1UnlcrPuajEieqZbl1zyLKbjeLJNTC0A7wOH95%2Fn7fLKSBb4obDYVbvvJ5aJP3g6%2BLDf3YaxqV3UFs%2BfnJCUIcTt4Dw6QfAWAAJMjhMjqJJ5SK3k5cqOpy17IcrM8gNTi2JQaxHxzoEsrxNtlKENdlKduU4eTrJkf729GC5lzy6tXhSRF%2BMpS7WfkqMqfOk2%2FeKqnjvvu88C4Qb83thKmZJ5XkbF9nBzBTn64ZklhumqvjB6i4pPXIYQv8MrnNb1Hdvq9wtwdLLzIeCCCQgeTLyEO6rcgYzcVrNFaNHqs5y8O8rPpOwS2iwbXHmSqfQuMrfqhD%2FuV%2FeMFTMVWoN%2F7fE5rVN6FzhY137aL%2BMvOX%2BWjl4dv8dzrzJ2tYpxKNAGGvO0Q%2FmcxwLID%2BBjFOh92LvN94wzxi8KL%2BJefKcDz90g2REVAMbVCLd3QoEroVMyYiD%2B4x8dx1jNKyLauy61fggtI0D0MNsGusDZA3YHdLqG6c9j39PWHmd%2BUNguJzZaVxoJmpprvlFBHeiSNCQvEt%2BSwluNxNdsWgdxB6uQB0hYNh7iDeckpD5y%2BiRnHnQwURflD9fuUEo6O%2B2lHtTTKCxpJlUVs9xAQQJXPyzk%2Bt20hjEsoyx4GtR8XB0lRFWbxcVPv8aWuW10SdltXmGwblkwhLewwL7W8EC9zy5VMpw7e4%2FRTk%2B4UP1IqJ%2FRbUx6ecG%2FvbO%2Fru1kAGwZ%2B6A%2BfiJ%2BVgr%2B%2F%2BZf6YS4nqeBwyzYJ7laeHim9a0dtnJ8j82YHZuiym%2F8pA3gpnNRR5%2FEz3q%2BT7e%2Fahu6vUAQH9%2B4ywayAB8vl3HWnOdNRbhREwivmozwY6jwHKE1kZYBIh0JqFR7XIEVM0g3sbXhyMSrR%2FEzNpdXKcwdUQMd886r47JIUb2m91%2FXte0UO4JuiZgz6gsjJ2pJlrI%2B77f1aVtYXExSTBkF32s%2F4j1fiNTVWAIgxHRxCGz7%2FoMmAeOyi%2FxtbWn0cvFIfxqHiNUul6L3Tsjn6jordLuGb5GyXEDF%2BU%2FVfJS3j1Vg%3D%3D&X-Amz-Signature=6d92b96605cb5a8919e8ba37f070a610a79f0cd0bde1c66177c4a9cf2c8fcf32&X-Amz-SignedHeaders=host&response-content-disposition=attachment)


3. Follow the Atlassian [guide](https://www.atlassian.com/migration/plan/cloud-guide) to migrate from Jira DC to Cloud.
   * **Important**: Don’t change Jira project names while migrating.
4. [Integrate Jira Cloud with Cobalt](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo).
5. Contact your Customer Success Manager to have findings with associated Jira issues in the old Jira DC instance reassociated with issues on the new Jira Cloud instance. Provide the following information:
   * Your organization name
     * URL of the old Jira DC instance
     * URL of the new Jira Cloud instance
     * [Tags](https://docs.cobalt.io/en-us/articles/glossary-YfTMKeZ1VM#h-pentest-tag) of pentests for which finding-to-ticket associations should be updated


:::info
**Note**

The Cobalt Jira plugin does not store any data that needs to be migrated. Jira tickets that were created for findings are stored in Jira similar to other tickets.

:::

## **Switching to a New Jira Cloud Instance**

Follow this guide if:

* You’re **not** migrating from Jira DC to Jira Cloud; and
* You’ve set up a new Jira Cloud environment and want to switch the instance connected with Cobalt.

You can reconfigure the integration in two ways:

* Option 1: Migrate existing tickets between Jira instances
* Option 2: Push findings to a new Jira instance

## **Option 1: Migrate Existing Tickets between Jira Instances**


1. Uninstall the Cobalt Jira plugin from your current Jira Cloud instance.
2. In Cobalt, delete the integration. Navigate to **Integrations** > **Jira**, and select **Delete**.
3. Follow the Atlassian [documentation](https://confluence.atlassian.com/adminjiraserver0818/migrating-projects-to-another-jira-instance-1167724774.html) to migrate projects between Jira instances. Migrate tickets related to findings.
   * **Important**: Don’t change Jira project names while migrating.
4. [Configure the integration](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo) between Cobalt and your new Jira Cloud instance.
5. Contact your Customer Success Manager to have findings with associated Jira issues in the old Jira Cloud instance reassociated with issues on the new Jira Cloud instance. Provide the following information:
   * Your organization name
   * URL of the old Jira Cloud instance
   * URL of the new Jira Cloud instance
   * [Tags](https://docs.cobalt.io/en-us/articles/glossary-YfTMKeZ1VM#h-pentest-tag) of pentests for which finding-to-ticket associations should be updated
   * Migration option you selected (Option 1: Migrate existing tickets between Jira instances)

## **Option 2: Push Findings to a New Jira Instance**


1. Uninstall the Cobalt Jira plugin from your current Jira Cloud instance.
2. In Cobalt, delete the integration. Navigate to **Integrations** > **Jira**, and select **Delete**.
3. [Install and connect the ](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo#h-step-1-connect-the-jira-plugin)**[Cobalt for Jira Cloud](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo#h-step-1-connect-the-jira-plugin)**[ plugin](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo#h-step-1-connect-the-jira-plugin).
   * **Important**: Do not configure integrations for pentests in Cobalt.
4. Contact your Customer Success Manager to have findings-to-ticket associations deleted. Provide the following information:
   * Your organization name
   * URL of the old Jira Cloud instance
   * [Tags](https://docs.cobalt.io/en-us/articles/glossary-YfTMKeZ1VM#h-pentest-tag) of pentests for which finding-to-ticket associations should be deleted
   * Migration option you selected (Option 2: Push findings to a new Jira instance)
5. In Cobalt, [configure the Jira Cloud integration for pentests](https://docs.cobalt.io/en-us/articles/jira-cloud-integration-0hggU8REdo#h-step-2-configure-the-integration-for-a-pentest).
6. [Enable auto-push](https://docs.cobalt.io/en-us/articles/push-cobalt-findings-to-jira-cdNUJlnblj#h-turn-auto-push-on-or-off) for pentests. Navigate to **Integrations** > **Jira** > **Configuration**, and turn on the **Auto-Push** toggle.

Findings in the Pending Fix state should be synchronized with your new Jira Cloud instance. If the synchronization doesn’t work, you can [push findings manually](https://docs.cobalt.io/en-us/articles/push-cobalt-findings-to-jira-cdNUJlnblj#h-push-findings-manually).

Switching to a New Jira Instance

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

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

Switching to a New Jira Instance

Share

Share

Switching to a New Jira Instance

Share

Share