Cloud Migration Guide

Welcome to the description of the migration path from the Column Order Gadget Server/Data Center Plugin to the Column Order Gadget Cloud Plugin. In this guide, we outline all necessary steps to migrate your gadget and the limitations of the migration path. Moreover, we present the feature parity of the Server/Data Center version and the Cloud version.

Migration

The only reason a manual migration of each dashboard gadget is required, is because there is no officially supported migration path for:

  1. dashboards

  2. filters & filter shares

  3. gadgets

Usually, the Atlassian partner doing the cloud migration for you will address all of these issues using custom tooling (at least for system gadgets). Column Order cloud was built with this scenario in mind and we will happily work together with your partner to automatically migrate Column Order gadgets as well. If you are interested, please reach out to us at support -at- celix -dot- at.

We start with a simple overview of the migration path. With the Column Order Gadget Migration it is possible to migrate the configured gadgets one-by-one:

Server gadget view
Server gadget configuration

Cloud gadget view
Cloud gadget configuration

 

Steps

This video will show you all the steps necessary to migrate your Column Order Gadgets to your Cloud instance. All steps shown in the video are also documented below.

Column Order Cloud Gadget Migration Path

 

  1. Go to the Server gadget and open the configuration view. Starting with Version 8.3.4 of the Column Order Gadget Plugin, you can now see the “Export config” button (highlighted with the red border).

     

  2. Click the “Export config” Button. This will store the configuration in your local clipboard.

  3. Now, go to the Cloud instance and create a new Column Order Gadget in the desired dashboard’s edit view.

  4. Here, you can see the “Import config” button (highlighted with the red border). Click it.

     

  5. This will bring up an input field for the configuration import.

     

  6. Go click inside this field and paste the exported configuration from the server plugin using Ctrl/Cmd+V.

  7. Now, all fields should be automatically configured, except the “Saved Filter” field. There are two different possibilities for this field:

    1. If your cloud instance already has a filter with the same name and JQL as the one used in the server gadget, then this field is also configured out of the box and the migration is complete. Please continue with Step 8.

    2. The filter used in the server gadget does not yet exist in the cloud instance.

      1. This means, we need to create it now. Therefore, you can use the button shown in the information field that showed up. Click it.

         

      2. The filter is automatically created and selected, if the JQL is valid in your cloud instance (i.e. all used fields, custom fields and methods exist). However, The filter is created as private filter for the user who imported configuration. You need to configure the visibility of the filter yourself afterwards.

      3. If the automatic creation is not successful, you can manually create and share the filter by clicking on the corresponding button. Afterwards, you need to manually select the created filter.

         

  8. As last step, you can use the “Show filter results” button to test the configuration.

Limitations

  1. As already mentioned in Step 7, it is not possible to automatically create each filter that was used in your server instance.

  2. Furthermore, it is also not possible to set the correct visibility on automatic filter creation. You have to do this manually after the filter is created.

  3. The filter’s column ordering is not migrated. This means, You have to configure it manually in case you are using “Use filter's Column Order” Option for the column ordering.

  4. Also, if you use a custom field and the custom field id from the server instance does not match the custom field id in the cloud instance, the view for this field does not contain useful content. The same is true, if the custom field does not exist in the cloud instance. Hence, you will have to delete the entry for such custom fields in the custom order configuration and newly add it, using the dropdown field in the configuration view.

 

Feature parity

 

Feature

Server / Data Center

Cloud

Feature

Server / Data Center

Cloud

View Filter results

Select any filter to view

Use the filters column order

Use the users column order

Use a custom column order

Periodic refresh (15min)

Link to Issue

View Issue Dialog

 

Issue Actions directly in the gadget

 

Issue Actions through Issue Dialog

 

Specify number of results per page (Pagination)

Manual migration from Server / Data Center to Cloud