Versions Compared

Old Version 20

changes.mady.by.user Oleksandra Kravets

Saved on

compared with

New Version Current

changes.mady.by.user Oleksandra Kravets

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If you and your team are moving from Jira Server/ Data Center to Jira Cloud, be sure - your checklists will be safely migrated as well.

There’re two methods of Jira Server to Cloud migration:

Note

Make sure you are aware of recommendations from Atlassian on Server → Cloud migration and plan it properly

Tip

For the features difference - check theServer & Data Center vs Cloud Comparison for Smart Checklist

Jira Site Import

Check how to use Jira Site Import to migrate from server to cloud

Your checklists will be migrated automatically.

Jira Cloud Migration Assistant (JCMA)

Check how to use the Jira Cloud Migration Assistant to migrate from server to cloud.

Anchor
JCMA_6.0.0
JCMA_6.0.0
For version 6.0.0 and higher

Preconditions

Server/Data center

  • update the Smart Checklist for Jira. Pro addon to the latest version;

  • update Jira Cloud Migration Assistant (JCMA) to the latest version.

Cloud

  • install the latest version of the Smart Checklist for Jira. Pro addon on your Cloud instance;

  • activate your Smart Checklist for Jira. Pro addon license/trial;

  • do not create custom fields `Checklists` and `Smart Checklist Progress` in advance.

JCMA flow

Navigate to Administration > System > Select “Migrate to cloud” in the left column.

Step 1: Assess your apps.

  1. Select Smart Checklist as an app that is `Needed in cloud`:

Step 2: Prepare your apps.

  1. Connect to your cloud instance.

  2. Check that you have Smart Checklist for Jira. Pro addon installed.

  3. Agree to migrate addon data.

Step 3: Assess and prepare your users.

  1. Connect to your cloud instance.

  2. Click “Begin assessing”.

  3. Fix invalid emails if needed.

  4. Choose from the offered options what to do with users that have invalid emails.

  5. Click “Review and apply”.

  6. Click “Apply to all migrations”.

Step 4: Review all email domains.

  1. Review and mark email domains as trusted so that you migrate users with only email domains you trust.

  2. Click “Done”.

Step 5: Migrate your data.

  1. Click “Create a migration”.

  2. Click “Connect to cloud”.

  3. Enter the name of the migration.

  4. Select migration stage.

  5. Select Cloud instance.

  6. Click “Choose migration options”.

  7. There are two available options: “Migrate all data” and “Choose what to migrate”.

  8. Select “Choose what to migrate”.

  9. Select Projects, Users and Groups, Customers, and Apps to migrate.

  10. Run pre-migration checks and fix errors if needed.

  11. Review migration.

  12. Run migration.

Post actions

Wait until your migration finishes and check its status for Smart Checklist for Jira. Pro addon:

  • If the migration status of the Smart Checklist for Jira. Pro addon data is “Completed” - the server part of the migration is successfully finished, you can wait for a few minutes and check your data on the Cloud instance:

  • In case during migration of the data some issues occur with data exporting from Server or connection to Cloud - migration status will be failed with error message available in the details:

You can check detailed logs for Smart Checklist migration by opening the page: /plugins/servlet/railsware/migrationlog

Panel
panelIconIdatlassian-flag_on
panelIcon:flag_on:
panelIconText:flag_on:
bgColor#FFEBE6

Smart Checklist content is migrated together with your project data.
This means you can’t  migrate Smart Checklist content for projects that are already available in the Cloud instance.

FAQ about Smart Checklist add-on migration in versions 6.0.0 and higher

Anchor
jcma_data
jcma_data
1. What data from Smart Checklist for Jira. Pro addon will be migrated from Server to Cloud?

We did our best to migrate all the data, but unfortunately, due to differences in Server and Cloud versions - there are some data types that will be available on Cloud in a different way or not available at all. Please see details information in the table below:

Data type

Migration support

Visibility on Server

Visibility on Cloud

Checklist items

Checklist items with different markup:

  • raw text

  • simple items

  • items with details

  • bold, italic, emphasized text

  • numbered lists

  • unnumbered lists

  • images

  • links to external sources

  • links to Jira (same project or different, but also migrated project)

Status
colourGreen
titlefully supported

Checklist items with dates

Status
colourBlue
titleSupported, different UI

  • all dates are visible in same color

  • dates in the past, current and future visible in different colors

Checklist items with real assignees

Status
colourBlue
titleSupported, different UI

  • id (username/login) is visible

  • user full name is visible

  • usernames of Smart Checklist item assignees are replaced with Cloud IDs during migration (visible on edit / “Checklists” custom field)

Checklist items with not-existed assignees

Status
colourBlue
titleSupported, different UI

Statuses

Default statuses

Status
colourGreen
titlefully supported

Custom statuses

Status
colourBlue
titleSupported, ORDER not KEPT

  • after migration it is needed to return needed order manually

Templates

Manual global / project templates (with trigger = none)

Status
colourGreen
titlefully supported

global

project

global

project

Global / project template with trigger “Issue created” without additional conditions

Status
colourGreen
titlefully supported

  • template is applied to all issues types

  • template is applied to all issue types

Global / project template with trigger “Issue created” with “Issue Type” condition (is one of / equals)

Status
colourGreen
titlefully supported

Global / project template with trigger “Issue created” with “Issue Type” condition (all issue types)

Status
colourGreen
titlefully supported

Global / project template with trigger “Issue created” with “Issue Type” condition (is not one of / does not equal)

Status
colourYellow
titlePartially supported

  • template applied based on conditions

  • template migrated without triggers (can be applied only manually)

Global / project template with trigger “Issue created” with any conditions different from “Issue Type”

Status
colourYellow
titlePartially supported

  • template applied based on conditions

  • template migrated without triggers (can be applied only manually)

Global / project template with triggers “Issue updated”, “Issue transitioned” with any extended conditions

Status
colourYellow
titlePartially supported

  • template applied based on conditions

  • template migrated without triggers (can be applied only manually)

Global template with “Multiple projects” selected

Status
colourBlue
titleSupported, different logic

  • template is visible on “Global templates” tab

Template will be saved as “project template” in migrated projects

Other

“Modify Smart Checklist” post function

Status
colourRed
titleNOT supported

not migrated, as feature not available in Cloud

“Smart Checklist Completed” validator

Status
colourRed
titleNOT supported

not migrated, as Cloud has different implementation

Smart Checklist history

Status
colourRed
titleNOT supported

not migrated

Anchor
sync_cloud_data
sync_cloud_data
2. I had custom fields “Checklists” and “Smart Checklist Progress” created on Cloud before I run JCMA, I don’t see migrated addon data in the Jira issues, what can I do?

In this case, after migration you will have duplicated custom fields:

Smart Checklist Addon on Cloud is using “Checklists” and “Smart Checklist Progress” custom fields to sync data in, so after migration to have migrated data saved to the addon database (and visible in the addon) - you need to synchronize data from custom field to addon database.

Note: this process runs in the background and may take some time before all the data finishes synchronizing.

Anchor
global_settings
global_settings
3. Will Smart Checklist global settings on the Server be migrated to Cloud?

Smart Checklist addon has the next settings based on versions:

Server / Data center

  • SC Addon visibility per Project

  • Display statuses for checklist items

  • Strikethrough checked items

  • Show on the customer portal

  • Notify assignees

Cloud

  • SC Addon visibility per Project

  • Display statuses for checklist items

  • Strikethrough checked items

  • Show on the customer portal

  • Notify assignees

Settings that are available only in Server - cannot be set up on the Cloud version.

Settings that are available in both versions are set up separately on different instances and are not migrated during JCMA migration.

Anchor
permissions
permissions
4. How access rights to Smart Checklist are migrated from Server to Cloud?

In the Server version - access to Smart Checklist is managed by Jira permissions, so permissions are migrated together with users and groups via the JCMA tool to Cloud.

On the Cloud instance, you can proceed with using default Jira permissions or configure custom permissions for the Smart Checklist add-on.

Anchor
JCMA_5.6.0
JCMA_5.6.0
For version 5.6.0 and lower

Pre-condition

"Checklists" custom field (mandatory) and "Smart Checklist Progress" custom field (optional) must be added to your Jira Server instance and must keep checklists' values.

Check the instructions on adding Checklists and Smart Checklist Progress custom fields to Jira Server (actual only for versions lower than v.5.0.0). 

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFFAE6

Please check if you use Custom Fields (Checklists, Smart Checklist Progress) for your Cloud instance before migration. They are optional for Cloud, but can be added manually by Jira Admin.

  1. Log in as a user with the JIRA Administrators global permission.

  2. Choose the cog icon at the top right of the screen, then choose Issues.

  3. Select Fields > Custom Fields to open the 'Custom Fields' page.

  4. Search for “checklist“ and check if there are two Custom Fields available: Checklists, Smart Checklist Progress

  5. If there are no results, then you can safely proceed with migration using JCMA tool.

  6. If the fields are present, please continue reading below:

If you would like to migrate Jira Server / Data Center to Jira Cloud instance with pre-created Custom Fields it will cause additional migratedCustom Fields creation which will not be available for Smart Checklist. These additional fields will store all the data from Jira Server / Data Center: Checklists (migrated), Smart Checklist Progress (migrated).

In this case you would need to copy all information from Checklists (migrated) to Checklists to restore the Smart Checklist data for each ticket.

At the same time, Smart Checklist Progress (migrated) field can be removed, because when you copy data to Checklists the Add-on will recalculate the existing Smart Checklist Progress field accordingly.

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFF0B3

Please note:

If you add the Checklists custom field after some time of using Smart Checklist, it is important that you first run the storage migration on the server side to ensure that all data is synced. Then you can proceed with migration to the cloud instance.

Migration

  • Run your migration with Jira Cloud Migration Assistant tool

    • custom fields “Checklists” and “Smart Checklist Progress“ will be created on the target instance (learn more about the Custom Fields) with checklists content

  • Then go to Apps → Manage Apps → Smart Checklist → Global Settings → Synchronize checklist storages

  • Click “Synchronize” button

  • The data from “Checklists” custom field would be transferred to a database and checklists per Jira issues will be created.

  • NOTE: the process may take a while. Make sure to run it out of working ours of your organization/

Templates Migration

Templates won’t be migrated automatically at this moment. You have to re-create them manually on the target Cloud instance one by one.

Follow the steps below

Expand
titleExpand to see the details

  1. Go to Checklist Templates on Jira Server/ Data Center

  2. Get the checklist template from the source Jira Server/ Data Center instance as a raw markdown text

  3. Paste the checklist to any Jira issue in target Jira Cloud

  4. Save Template

  5. Proceed with the rest of the templates

  6. You may also use Full-Screen Editor for checklist adding/editing

Can I Migrate my Smart Checklist for Jira Server/ Data Center License to Jira Cloud?

Unfortunately, no. Smart Checklist for Jira Server/ Data Center license is a one-time purchase with optional maintenance, whereas Cloud purchases are recurring subscriptions. As such, existing Server/ Data Center app licenses cannot be transferred or credited to Cloud. These are independent licenses that need to be paid for separately.

Info

If you already purchased your Jira Server/ Data Center license via the Atlassian Marketplace, you may contact Atlassian Support to see if you are eligible for a refund.

Insert excerpt
Get Started
Get Started
namesupport-email (checklist-server)
nopaneltrue