Migration to cloud

Subtasks Navigation for Jira provides the ability to migrate plugin data from the server version to the cloud. The migration is an automatic process done using Jira Cloud Migration Assistant.

What is going to be migrated?

Subtasks Navigation for Jira is showing a panel with sibling subtasks on the subtask issue view. The user is able to configure only the visibility of the panel per project. The migration process will migrate this configuration to the cloud. If the project was migrated from server to cloud, the configuration of visibility will be based on the project from server Jira.

Because the cloud Jira has no specific agile view and the cloud version of Subtasks Navigation for Jira has no progress bar feature, we will migrate only the option Enabled in issue view.

 

How should I migrate?

1. Ensure Jira Cloud Migration Assistant is installed in the server Jira

Jira Cloud Migration Assistant is a free plugin from Atlassian that is able to make your migration to Jira as easy as possible. It’s able to migrate the data from your Jira instance, but also 3rd party plugins that support this migration platform. Newer versions of Jira include the Jira Cloud Migration Assistant by default. If your server instance doesn’t have it, please install the plugin from Atlassian Marketplace.

2. Install the cloud version of Subtasks Navigation for Jira

Jira Cloud Migration Assistant (JCMA) allows you to review which applications you want to use in the cloud or find alternatives if the application has no cloud version. As a part of the migration process, you will be prompted to install the cloud version of Subtasks Navigation. It’s not necessary to do it from JCMA though. You can visit your cloud instance any time before the migration and install the cloud version from Atlassian Marketplace.

If you’re already using the cloud version of plugin and you still want to migrate project settings, you should disable and enable the cloud version to ensure, the migration endpoint is registered by your cloud Jira instance.

3. Migrate using the JCMA

You can use the JCMA to migrate everything at once (your Jira projects, users, applications,…) or just the Subtasks Navigation, if you already migrated your Jira data in the past. The only requirement is, that your projects should be already migrated or they should be migrated together with the application. You can run the migration process multiple times, just for the Subtasks Navigation for Jira, if you need.

You will find the documentation on how to use JCMA on the official Atlassian support website.

The migration status is visible also in the detailed view.

Failed migration usually means we are not able to find a relation between the Jira server project and the Jira cloud project. It could mean the project in the cloud was removed during the migration. The cloud plugin also communicates with the cloud Jira and when some request fails, the migration will fail too. In these cases, you should be notified about the problem by message in the view you can see above.

Waiting 8-10 minutes for the migration is usually normal. The data migration itself is faster, but it can take a while before the progress report is updated by the Jira.

In rare cases, when the migration process is stuck for hours, don’t hesitate to contact our support for further help.