Detected country: US
logo
API Docs

Getting Started

  • How to get started with Cobalt

Assets

  • Assets are what we pentest
  • Asset Types
  • Create an Asset
  • Risk Advisories

Pentests

  • Pentests
  • Create a Pentest
    • Overview
    • Asset Details
    • Pentest Details
    • Scope & Test Period
    • Preparation
  • Create an Autonomous Pentest
    • Launch a Saved Autonomous Pentest
    • Review a Closed Autonomous Pentest Report
  • Pentest Process
  • Pentest States
  • Coverage Checklist
  • Pentest Expectations
  • In House Pentests
    • Complete an In-House Pentest (For Pentesters)
    • Set Up an In-House Pentest
  • Findings
    • Remediate Findings
    • Finding States
    • Severity Levels
  • Reports
    • Contents of a Pentest Report
    • Customize Your Report
    • Co-branded Reports
  • Preparation

Engagements

  • Engagements Overview
  • Digital Risk Assessment
  • Secure Code Review

Findings

  • Findings

Insights

  • Insights

Planning

  • Planning

Methodologies

  • Cobalt Methodologies Overview
  • Web Methodologies
  • Autonomous 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

Attack Surface

  • Attack Surface Monitoring (ASM)

DAST Scanner

  • DAST Scanner Overview
  • Best Practices
  • FAQ
  • Integrations
  • Partial Scans: Reduced Scope
  • Scans
  • Sequence recorder
  • Targets
  • Target Authentication
  • Extra Hosts
  • Blackout Period

User Account

  • Account Overview
  • Account Settings
  • Password Best Practices
  • Sign In to Cobalt
  • Troubleshoot Sign-in Issues

Collaboration

  • Collaboration Overview
  • Collaborate on Pentests
  • Groups
  • Manage Pentest Collaborators
  • User Roles and Permissions
  • Manage Notifications

Organization

  • Organization Overview
  • Manage Users
  • Your Cobalt Contract
  • Configure Organization Settings
    • Configure SAML SSO
    • SAML Migration: Update Your Configuration
    • SCIM Provisioning Setup Guide

Credits

  • Cobalt PtaaS Tiers
  • Cobalt Credits
  • Track Your Credits

Integrations

  • Cobalt Integrations Overview
  • Integration Builder
    • Connect your applications
    • How to Guides
      • Create Azure DevOps Work Item for Findings
      • Create GitHub tickets for Findings
      • Create GitLab tickets for Findings
      • Send email notifications for Findings from Outlook
      • Send MS Teams notifications for Findings
      • Create Jira tickets for Findings
      • HTTP Connector
      • Import Assets from Google Sheets
      • Map Cobalt Pentest Finding Severity to Jira Issue Priority
      • Modify Jira Issue Summary to contain Pentest Title
    • Troubleshooting
  • Integrate Jira with Cobalt
    • 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
  • Slack
  • Microsoft Teams
  • Webhooks
  • DefectDojo
  • Kenna Security
  • Vanta
  • Carried Over Findings
  • Create Test Finding
  • Wiz

Cobalt API

  • 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

Glossary

  • Glossary

What's New

  • May 2026
  • April 2026
  • 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
  • Product Updates
  • August 2026
‌
‌
‌
logo

Powered by

Assistant

Ask new question

Powered by
  • Home
  • Integrations
  • Integrate Jira with Cobalt
  • Switching to a New Jira Instance

Switching to a New Jira Instance

2min read

Share

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.

  1. Follow the Atlassian guide to migrate from Jira DC to Cloud.
    • Important: Don’t change Jira project names while migrating.
  2. Integrate Jira Cloud with Cobalt.
  3. 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 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 to migrate projects between Jira instances. Migrate tickets related to findings.
    • Important: Don’t change Jira project names while migrating.
  4. Configure the integration 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 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 Cobalt for Jira Cloud 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 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.
  6. Enable auto-push 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.

Share