| Align | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||
|
In this last step, you will further refine the setup for Salesforce & JIRA Cloud Connector.
At the end of this step:
Your new connector will be ready for usage.
Prerequisites
You have completed Step 4 - Configuring Salesforce.
You have administrator access to JIRA Cloud.
You have administrator access to Salesforce.
Post-migration notes
Disable the Classic Connector
...
| Tip |
|---|
This also lets Atlassian and ServiceRocket know that you are done with the migration. |
Log in to JIRA Cloud.
From the Cog Icon
...
, choose Add-ons.
Under Atlassian Marketplace menu section, choose Manage add-ons.
You will see a list of available add-ons.
Disable these add-ons in the following order:ServiceRocket Salesforce.com Connector Plugin - Plugin
ServiceRocket JIRA Connector - Plugin
ServiceRocket Core Connector - Plugin
Note that at the end of the migration window, Atlassian will remove these add-ons completely from all JIRA Cloud instances.
...
The New Connector offers some new features and settings that were not available in the Classic Connector. We recommend you to review the settings as per the Administrator guide.
Review the user guides
It might be helpful to send your users some resources to get familiar with the New Connector. Take a look at at User guideGuide.
License and subscription
Your New Connector should already have a matching expiry date as mentioned in Migrating to the Cloud Connector (Archived). Note that by the end of the date, you will need to re-subscribe to the New Connector. This is a requirement by Atlassian to ensure the license is migrated successfully.
Questions? Problems?
Contact our support team or email us at support@servicerocketsupport@appfire.com.