Migrating from Server or DataCenter to Cloud

Below are instructions on how to migrate AssertThat BDD, Cucumber & Test Management 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

 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 & Test Management for Jira plugin for the projects that you are going to migrate on the Cloud instance. AssertThat Configuration & Enable for project

  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 Bitbucket

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

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

    { "jira_server_url": "http://mycompany-jira.com", "jira_server_username": "", "jira_server_password": "", "jira_cloud_url": "https://mycompany.atlassian.net", "jira_cloud_username": "admin@example.com", "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 with admin access to projects.
    jira_server_password - The password of the Jira Server/DC user with admin access to projects.
    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 The Jira Cloud platform REST API
    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 the default set to https://bdd.assertthat.app

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

    python get-server-projects.py
  5. Explore the ./output/server-projects.json and exclude projects that 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 the project configuration page in Jira Cloud AssertThat Configuration & Enable for project

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

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

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

     

  10. Run Re-indexing Using AssertThat scenario properties in JQL search | Reindexing

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