Migrating from Server or DataCenter to Cloud

Below are instructions on how to migrate AssertThat BDD & Cucumber for Jira plugin from Jira Server or Data Center to Jira Cloud

Differences between Server/DC and Cloud versions of the app

Feature

Jira Server/Data Center

Jira Cloud

Feature

Jira Server/Data Center

Jira Cloud

Features/scenarios upload and management

Scenario Manager

Traceability Matrix

Automated Test Report

Link Scenarios to User Stories

Manual Scenarios execution

AssertThat Test Plans

*Being implemented

*https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/2203189257 is not currently available on Jira Cloud. This functionality is being implemented and will be available soon. Please refer to https://www.assertthat.com/post/roadmap-q1-2022-q2-2022

 Migration instructions

Prerequisites:

  1. Install https://marketplace.atlassian.com/apps/1219033/assertthat-bdd-cucumber-for-jira?tab=overview&hosting=cloud plugin on your Jira Cloud instance

  2. Enable AssertThat BDD & Cucumber for Jira plugin for the projects which you are going to migrate on the Cloud instance. https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/725385217

  3. Download and install Python on the instance you are going to use for running migration scripts https://www.python.org/downloads/

In order to retain the linkage between scenarios and user stories Jira Server/DC project key and Jira Cloud project key should match exactly.

Migration steps

  1. Clone repository https://bitbucket.org/AssertThat/assertthat-bdd-cloud-migration/src/master/

  2. Install dependencies. Run
    pip install -r requirements.txt

  3. Update global configuration in ./config/global.json

    1 2 3 4 5 6 7 8 9 { "jira_server_url": "", "jira_server_username": "", "jira_server_password": "", "jira_cloud_url": "", "jira_cloud_username": "", "jira_cloud_api_token": "", "asserttthat_host": "https://bdd.assertthat.app" }

    jira_server_url - The url of your Jira server or Data Center instance e.g https://jira.mycompany.com

    jira_server_username - The username of the Jira Server/DC user which has access to the projects which are being migrated.
    jira_server_password - The password of the Jira Server/DC user which has access to the projects which are being migrated.
    jira_cloud_url - The URL of the cloud Jira instance where the projects are being migrated to e.g. https://mycompany.atlassian.net
    jira_cloud_username - The email address of the Jira Cloud user which has Browse users and groups global permission. More details here https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get
    jira_cloud_api_token - API token of the Jira cloud user used in jira_cloud_username https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/
    asserttthat_host - Leave as default set to https://bdd.assertthat.app

  4. Run ‘get-server-projects.py' script, which will create a file ./output/server-projects.json

    1 python get-server-projects.py
  5. Explore the ./output/server-projects.json and exclude projects which are out of scope of the migration.

  6. For each project in ./output/server-projects.json fill in the corresponding Jira cloud project details
    jira_cloud_project_id, assertthat_access_key, assertthat_secret_key which can be found on project configuration page in Jira Cloud https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/725385217

  7. Run 'migrate-config.py' which will migrate projects configurations from Jira Server/DC to Cloud

    1 python migrate-config.py
  8. Run 'migrate-features.py' which will migrate the features from Jira Server/DC to Cloud

    1 python migrate-features.py
  9. Run 'migrate-executions.py' which will migrate manual execution results for each of the Scenarios which are linked to Jira story.

    1 python migrate-executions.py

In case of any issues or questions please reach us at support@assertthat.com