Switching to a New Jira Instance
Learn how to reconfigure your Jira integration with Cobalt.
Learn how to reconfigure your Jira integration if you:
Migrating from Jira Server/DC to Jira Cloud
If you’re migrating entirely from Jira Server/DC to Jira Cloud, do the following:
- Uninstall the Cobalt Jira plugin from your Jira Server/DC.
- In Cobalt, delete the integration. Navigate to Integrations > Jira, and select Delete.
- Follow the Atlassian guide to migrate from Jira Server/DC to Cloud.
- Important: Don’t change Jira project names while migrating.
- Integrate Jira Cloud with Cobalt.
- Contact your Customer Success Manager to have findings with associated Jira issues in the old Jira Server/DC instance reassociated with issues on the new Jira Cloud instance. Provide the following information:
- Your organization name
- URL of the old Jira Server/DC instance
- URL of the new Jira Cloud instance
- Tags of pentests for which finding-to-ticket associations should be updated
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 Server/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
- Uninstall the Cobalt Jira plugin from your current Jira Cloud instance.
- In Cobalt, delete the integration. Navigate to Integrations > Jira, and select Delete.
- Follow the Atlassian documentation to migrate projects between Jira instances. Migrate tickets related to findings.
- Important: Don’t change Jira project names while migrating.
- Configure the integration between Cobalt and your new Jira Cloud instance.
- 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
- Uninstall the Cobalt Jira plugin from your current Jira Cloud instance.
- In Cobalt, delete the integration. Navigate to Integrations > Jira, and select Delete.
- Install and connect the Cobalt for Jira Cloud plugin.
- Important: Do not configure integrations for pentests in Cobalt.
- 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)
- In Cobalt, configure the Jira Cloud integration for pentests.
- 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.
Last modified November 14, 2024