Post-migration steps

Owned by Nirosan (Unlicensed)
Last updated: Oct 31, 2023 by Elizabeth Tai (Unlicensed)
3 min read

Configure the contents highlighted on this page to ensure that when you disable the Classic Connector, your existing URLs, connections, post-functions, and other features do not break or stop working.

Salesforce package installation

If you have skipped the package installation in this step: Step 5 - Installing the Salesforce package or you have clicked Continue by accident, read this section.

If you are using any Classic Connector feature in Salesforce, you need to install the package.

URLs endpoints configured on the Salesforce platform to create Jira issues, fetch Jira issues and other connections made with Jira from the Salesforce platform will stop working.

To resolve this issue, follow the Installing the Salesforce Package guide.

Jira project workflow post-function configuration

If you have finalized your migration in this step: Step 6 - Finalizing the migration or you clicked Finalized by accident, read this section.

If your Classic Connector uses workflow post-functions, you need to reconfigure the workflow.

Any post function created in your Jira project workflow that linked to the Salesforce platform will not work anymore.

To resolve this issue, read the Configuring workflow post functions in Jira guide to add workflow post-functions in the NextGen Connector.

Updating bindings to use the same connection

  • In Connector for Salesforce & Jira Server (NextGen), one connection can be associated to multiple objects.

  • In both the Classic and Next-gen connectors, associations are tied to their respective mapping schemes/bindings and connections. The app migrates everything as is.

Problem

In this scenario, you have multiple connections in Classic Connector for Salesforce & Jira and they all point to the same Salesforce Instance URL. Each connection is associated with one Salesforce object type.

After migration, you are allowed to set up one of these connections over on the Salesforce package.

Solution

In this scenario, both connections A and B point to the same Salesforce Instance URL, and each connection is linked to one Salesforce object.

  • Connection A → Salesforce Case (Authorized)

  • Connection B → Salesforce Opportunity (Not Authorized)

These connections are not redundant, and users are not encouraged to remove them, or risk losing most of the sync functionalities.

Both of the connections can be authorized but only one of these connections can be set up on the Salesforce package. In this case, we may want to consider consolidating all the connections pointing to the same Salesforce organization.

  1. If we want to merge Connection A and B, we want to first make sure that Connection A supports the Salesforce object type configured in Connection B.

  2. Under Operations, click Configure for Connection A.

  3. Under Available Salesforce Objects, click Add Salesforce Object.

  4. Add the “Opportunity” object here, and Click Apply Changes to complete the configuration. We add all the connections' objects and consolidate them into one connection.

  5. Next, we go to the Bindings page and click Edit on each migrated binding. We ensure that the binding points to the connection (Connection A) which has all the Salesforce object types consolidated from the other connections.

With this, we have ensured that all the bindings are pointing to the right connection, which we can use to set up the Salesforce package. Once this is done, the other migrated connections which were consolidated, can be safely removed.