Changing the URL or Transitioning Between Instances

To update your URL or switch instances (e.g., from Jira Cloud to Jira Data Center), Getint offers a straightforward process to adjust connections within integrations for a smooth transition. This guide outlines the necessary steps for changing your URL or transitioning to a new instance.

How to Change the URL in Your Integration

If your Jira Cloud URL has changed:

1. Open the option to create an integration in Getint.

1. Follow the steps to establish a new connection using the new URL (if you haven't already) and exit the creation tab. For further instructions, refer to our Connection guide.

1. Open the integration you want to modify, click More > Settings in the top right, disable it, and save.

1. Select the app icon you want to change.

1. Choose Change Connection.

1. Select the new connection and select Change Connection.

1. Save the changes and re-enable the integration.

Transitioning Between Jira Instances

If you’re transitioning between Jira instances, such as moving from Jira Data Center to Jira Cloud:

1. Create a New Connection:

   • Set up a new connection with the appropriate URL and credentials for the new Jira instance.

   • Ensure the new connection has the same permissions as the previous one to avoid data sync issues.

2. Edit the Integration:

   • Go to the Integration Editor and update the connection to point to the newly created one.

3. Test the Sync:

   • Verify that data syncs correctly between the new instance and the destination app.

Warning: Switching from Jira Data Center to Jira Cloud (or vice versa) by simply updating the connection may not work due to key structural differences between the two platforms, including: ✔ Field IDs – Jira Cloud and Jira Data Center assign different internal IDs to custom and system fields, which may break mappings. ✔ Project IDs – Each Jira instance generates unique project IDs, making direct migration difficult. ✔ User IDs – Jira Cloud uses Atlassian Accounts, while Jira Data Center may rely on internal directories or LDAP, causing user mismatches. ✔ Field Names & Workflows – Some fields, workflows, and statuses may not be identical, leading to synchronization issues or failed updates.

If you’re moving between Jira Cloud and Jira Data Center, we strongly recommend using Getint’s Migration option to ensure a proper migration rather than just changing the connection.

When to Use the "Change Connection" Feature

The Change Connection feature is designed to help with:

• URL Changes: For example, updating your Jira Cloud instance URL.

• Account Updates: Switching from a personal account to a service account.

• Connection Errors: Resolving connection-related issues by switching to a new connection.

Best Practices and Considerations

Pros:

• Easily update your connection without creating a new integration.

• Seamlessly transition between accounts or fix connection issues without affecting existing data.

• Supports URL changes for the same instance.

Cons:

• Ensure the new connection has identical permissions to access fields and issues already synced; otherwise, data sync errors may occur.

• Avoid using this feature for significant changes, like switching projects or migrating between fundamentally different instances (moving to a different app, for example)

For more detailed modifications, you can access the Connections settings in the Workflows section of Getint. Refer to our Connections Documentation for additional guidance.

Conclusion

Getint's connection management features simplify the process of changing URLs or transitioning to a new instance. Ensure the new connection's permissions align with the previous ones to prevent disruptions.

For additional support, reach out to our Support Portal.

Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!