Jira Server/DC to Cloud Migration Guide

For customers migrating from Jira Server to Cloud, this article describes how to properly re-configure Cobalt's Jira integration with your new instance.

 

Migration of Jira Server/DC data to Jira Cloud

If you are migrating entirely from Jira Server/DC to cloud, follow the steps below. 

1. Uninstall the Cobalt Jira plugin from Server/DC

2. Disconnect the Jira integration in the Integrations Hub of the Cobalt web-app

3. Follow an official Atlassian guide for migrating from Server/DC to Cloud (example: https://www.atlassian.com/migration/plan/cloud-guide). Do not change Jira project names while migrating.

4. Install and configure the Cobalt Jira Cloud integration

5. Contact your CSM to have findings with associated Jira issues in the old Jira Server re-associated to issues on the new Jira Cloud instance.  Please provide the following information: 

   • Client organization name

   • URL of the old Jira server

   • URL of the new Jira cloud instance

   • The tags of pentests for which finding-to-ticket associations should be updated

   • Which integration path the customer is following

Switch Jira Instance Connected to Cobalt Platform

If you are not migrating your Jira data from Server/DC to Cloud,  but have set up a new Jira Cloud environment and want to switch which instance is connected with the Cobalt platform, follow the steps below. 

Path A - Migrate existing tickets between Jira instances:

1. Uninstall the Cobalt Jira plugin from Server/DC

2. Disconnect the Jira integration in the Integrations Hub of the Cobalt web-app

3. Follow an official Atlassian guide for migrating tickets between Jira instances. Migrate tickets related to findings. Do not change Jira project names while migrating.

4. Install and configure the Cobalt Jira Cloud integration

5. Contact your CSM to have findings associated to tickets on the old Jira server re-associated to tickets on the new Jira cloud instance. Provide the following information:

   • Client organization name

   • URL of the old Jira server

   • URL of the new Jira cloud instance

   • The tags of pentests for which finding-to-ticket associations should be updated

   • Which integration path the customer is following

Path B - Push findings to new Jira instance:

1. Uninstall the Cobalt Jira plugin from Server/DC

2. Disconnect the Jira integration in the Integrations Hub of the Cobalt web-app

3. Install and connect the Cobalt Jira Cloud integration. Do not configure integration settings for pentests in the Cobalt web-app.

4. Contact your CSM to have findings-to-ticket associations deleted. Provide the following information:

   • Client organization name

   • URL of the old Jira server

   • The tags of pentests for which finding-to-ticket associations should be deleted

   • Which integration path the customer is following

5. Configure the Jira cloud integration for pentests

6. Turn on auto-push for pentests. Tickets in the pending_fix state should be syncronized to the new Jira cloud instance. If this does not work then use the manual “push to Jira” button in the UI

FAQs

Q: Does the Jira server/DC plugin store any data that needs to be migrated?

A: No, the Jira plugin does not store any data that needs to be migrated. Jira tickets that have been created for findings are stored in Jira the same way as other tickets.

Q: What is a pentest tag?

A: A pentest tag is the PT# in the red rectangle in this example screenshot