Versions Compared

Key

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

...

  • Applicable global settings

  • Chat Settings for JSM settings for all the migrated Jira projects

  • Agents online/offline schedule

  • Translations

  • Chat conversations from signed-in and anonymous users

  • Chat conversations' metadata (including custom metadata)

...

  1. Ensure that you have the latest version of Chat for Jira Service Management Server.

  2. Ensure that you have Chat for Jira Service Management installed on your Cloud instance.

  3. Run a migration of your Jira Service Management projects with the Chat add-on selected for migration.

  4. To walk around this issue with the Jira migration tool, uninstall Chat for Jira Service Management on the Cloud instance and re-install it.

  5. Run another migration. This time select no projects, but add to the scope only Chat for Jira Service Management.

  6. Verify that the data is migrated:

    1. Go to the Global Chat Settings page and verify that the settings supported in Cloud are migrated.

    2. Go to the Translate and Customize page, and verify that translations have been properly migrated.

    3. Go to the Chat Settings Project Settings > Chat for JSM page for each of the migrated projects, set Issue Type for Chat, and verify settings there.

    4. On the Chat Settingsfor JSM page, disable and enable Chat of the migrated projects in order to see Chat Dashboard in them.

    5. Ask each Jira Service Management agent to verify if their Chat schedule has been migrated.

    6. Go to the Chat Dashboard page for each of the migrated projects and validate if the conversations have been migrated.

...

After migrating from Server to Cloud, you will have to update your Chat Settings settings inside your service project. If you are using Chat Widget on an external website, you should update your Chat Widget JavaScript code on your external website according to the provided code in Chat Settingsfor JSM settings.