Migrate your Jira integration

If you're an existing qTest customer with an active Jira integration and you plan to migrate your Jira data to a different Jira instance, you must reach out to your Tricentis Customer Growth Account Manager (CGAM) to relink your Jira as part of the migration.

This topic covers when you need to relink during a migration, what you need to prepare, how to request the engagement, and what to expect during the process.

You can't update the Jira integration URLs from the qTest, as the relinking process requires a database administrator to run specific queries that update back-end database fields. This is why Tricentis Professional Services (PSO) must perform the work. This won't cost you anything. The relinking effort is currently scoped as a $0 engagement, delivered under a formally documented Statement of Work.

What migration looks like

A full Jira migration with qTest relinking follows these steps:

  1. Confirm your decision to migrate to another Jira instance.

  2. Work with Atlassian to plan and prepare Jira migration.

  3. Work with Tricentis to plan the qTest relinking activity.

  4. Work with Atlassian to review Jira Cloud rate-limiting considerations.

  5. Complete your Jira migration.

  6. Tricentis executes the qTest relinking process.

Your relinking and migration timeline

Plan for approximately one month end-to-end, including planning, migration, relinking, and validation. Within that window:

  • Expect Jira migration planning and execution to take several days to a week, depending on scale.

  • Implement a blackout period during relinking and migration, where users must not modify Jira or qTest data.

  • Give a few weeks of lead time for planning and scheduling with Tricentis PSO.

When you need to relink your Jira integration

You must relink your Jira integration anytime you migrate from a Jira instance already connected to qTest to a new Jira instance: On-Premise to On-Premise, On-Premise to SaaS, and SaaS to SaaS.

This is relevant if your organization is using any of the following Atlassian platforms with end-of-support announcements:

  • Jira Server: Support ended February 15, 2024.

  • Jira Data Center: Support ends January 22, 2027.

  • All Atlassian Data Center products: Read-only as of March 28, 2029.

What happens if you skip relinking

If you skip relinking with your CGAM, you may encounter unrecoverable data corruption.

Without relinking, existing qTest integrations continue to point to the old Jira instance, which results in:

  • Updates made in qTest sent to the old Jira system.

  • Jira updates that fail if the old system has been decommissioned.

  • Users that encounter synchronization errors or outdated data.

  • Old Jira objects that are unintentionally updated.

What you'll work on with Atlassian

Before we can start relinking, you'll need to complete a couple tasks with Atlassian.

Complete the Jira migration

Work with your Atlassian team to perform the Jira migration. As part of this migration, your Jira project must exist in both source and target Jira instances, and Jira issue keys must remain identical before old and new Jira projects.

If issue IDs don't match between the old and new Jira projects, we can't successfully complete the relinking process.

Plan for Jira rate limiting

Work with your Atlassian Customer Success Representative to schedule time when Jira Cloud rate limiting can be disabled. If Atlassian can't disable rate limiting, you must temporarily increase it increased for the duration of the sync.

This makes sure that all objects from the new Jira instance are properly synced with qTest using the new Jira instance integration before the relinking script runs. For more information, see Jira rate limiting.

What you'll work on with Tricentis

Here's the information you'll need to provide us, and the steps we take to fully relink your qTest and migrated Jira project.

How to schedule relinking

To start a relinking engagement, contact your CGAM and let them know you're planning a Jira migration that requires a qTest-Jira relinking engagement.

Include the following details in your request for your CGAM to coordinate with PSO:

  • The number of qTest projects in scope.

  • Your estimated Jira migration start date.

  • Your target completion date.

  • URL to the old Jira instance.

  • URL to the new Jira instance.

What we'll do during relinking

When we relink your migrated Jira, we verify with your Atlassian Customer Success Representative that rate limiting is disabled or increased. Then, we validate Jira integrations for each qTest project in the scope, retrieve Jira objects into qTest, and verify object counts. Finally, we validate that all links are updated and working as expected.