Data Transfer

During your upgrade, the Jira settings and permission will stay the same. The following data will be migrated:

Test cases fields

Squad test case fields

Scale test case fields

Migration path

Summary

Name

We migrate the Squad test case "Summary" field to the "Name" field inside the Scale test case.

Description

Objective

We migrate the Squad test case "Description" field to the "Objective" field inside the Scale test case.

Status

Status

We extract the data about issue statuses from Jira("To Do", In Progress", "Done", etc) for this project and use this data to re-create these statuses as custom statuses for test cases in Scale and then assign them accordingly to test cases migrated from Squad to Scale.

Assignee

No equivalent inside the test case creation in Scale.

We create a custom field for test case in Scale with type user picker called “Assignee“ and map Squad Assignee there.

Labels

Labels

We need to extract labels for test case from Squad and migrate them to Scale.

Sprint

No equivalent inside the test case creation in Scale.

Sprint Field from Squad will become a test case custom field(Select list Multi-choice) in Scale with the name "Sprint" that contains the data from Squad.

Story point estimate

No equivalent inside the test case creation in Scale.

WE ARE NOT MIGRATING THIS FIELD. There is no use of story points in Scale.

Fix versions

No equivalent inside the test case creation in Scale.

The "Fix versions" Field from Squad will become a test case custom field(Select list Multi-choice) in Scale with the name "Fix versions" that contains the data from Squad test case “Fix Version“ field.

Affected versions

No equivalent inside the test case creation in Scale.

If the value exists, “Affected version” field will be migrated as a custom field called “Affected version“(Select list Multi-choice) for Scale test case.

Reporter

Owner

We migrate data from the "Reporter" field in Squad to the Scale test case field "Owner".

Priority

Priority

We are migrating all priorities as custom ones and then assigning them according to the migrated test cases.

Due date

No equivalent inside the test case creation in Scale.

We are migrating “Due Date” field from Squad as custom field called “Due Date” to Scale with the type Date picker.

Original estimate

Estimated time

We need to transform the data into the hours and minutes format (hh:mm) and if the value will be bigger than 99h:59m. We truncate it to fit 99h:59m and assign this value to the "Estimated time" field in the Scale Test case.

Time Tracking

No equivalent inside the test case creation in Scale.

WE ARE NOT MIGRATING THIS FIELD. “Time tracking“ for Squad test case represents the logged time. It's equivalent in Scale is represented by the field "Actual" inside the test player.

Start dates

No equivalent inside the test case creation in Scale.

If the value exists, we are migrating “Start dates” field from Squad as custom field called “Start dates” to Scale with the type Date picker.

Environment

No equivalent inside the test case creation in Scale.

If the “Environment“ field for Squad test case is not empty we need to create a custom field in Scale called “Environment“(type: Text Field (Multi-Line)) and transfer Squad data to this field in Scale.

Component

Component

If the component field in Squad contains multiple component values, one of the components needs to be assigned to the component field for the Scale test case and all others need to be mapped to the Scale test case custom field called “Squad components“ with the type Select List (Multi Choice).

Epic link

Test case → traceability tab → Issue

When we have an epic link we need to link it to Jira issue inside the traceability section of the test case

Issue links

Test case → traceability tab → Issue

When we have an issue link we need to link it to Jira issue inside the traceability section of the test case

Comments

Comments

We migrate comments as it is from Squad test case to Scale test case

Attachments

Attachments

We migrate attachments as they are.

Subtasks

Test case → traceability tab → Issue

When we have an sub-task link we need to link it to Jira issue inside the traceability section of the test case

Test case custom fields

All of them will be migrated except the one with Jira Advanced type

Squad

Scale

Checkboxes

Select List (Multi-Choice)

Date picker

Date Picker

Date time picker

Date Picker

Labels

Select List (Multi-Choice)

Number field

Number

Radio Buttons

Select List (Single Choice)

Select list (cascading)

N/A

Select list (multiple choices)

Select List (Multi-Choice)

Select list (single choice)

Select List (Single-Choice)

Paragraph (supports rich text)

Text Field (Multi-Line)

Short text (plain text only)

Text Field (Single-Line)

URL Field

Text Field (Multi-Line)

User Picker (single user)

User Picker

Test case linked issues

We extract linked issues from the Squad test case and link them to the Scale test case in the traceability section.

Test case steps: step, data, and result

Squad

Scale

Test step

Step

Test Data

Test Data

Test Result

Expected Result

Attachments

Attachments

Custom fields

Custom fields

Test case step attachments

We migrate test case step attachments as they are.

Test case step custom field

Squad

Scale

Text Field (single line)

A basic single line text box custom field to allow simple text input.

Text Field (Single Line)

Text Field (multi-line)

A multiline text area custom field to allow input of longer text strings.

Text Field (Multi-Line)

Number Field

A custom field that stores and validates numeric (floating point) input.

Number

Radio Buttons

A list of radio buttons.

N/A

Checkboxes

Choose multiple values using checkboxes.

Checkboxes

Select List (single choices)A single select list with a configurable list of options.

Select List (Single Choice)

Select List (multiple choices)Choose multiple values in a select list.

Select List (Multi-Choice)

Date Picker

A custom field that stores dates and uses a date picker to view them.

Date Picker

Date Time PickerA custom field that stores dates with a time component.

N/A

Test case change history

To migrate Squad test case history to Scale we need to combine data from the Jira issue history and the “Test Details History” tab.

From the “Test Details History” tab we need to get data about changes made to Squad test steps.

From the Jira issue history, we need to get all the data available there.

After getting the data from both Squad histories we need to sort it based on the time that the change was made. (sort by date and time to get the right order.)

After sorting the data we import it to Scale as a separate change event to the test case.

Test cycles fields

Squad

Scale

Version

Release version

Name

Name

Description

Description

Build

Text custom field

Environment

Text custom field

From

Test cycle Planned start date

To

Test cycle Planned end date

Test execution fields

Squad

Scale

Test execution key/id

Test execution key/id

Summary

Summary

Description

Objective

Execution Status

Execution Status

All Execution Statuses - UNEXECUTED, PASS, FAIL, WIP, BLOCKED, Custom

UNEXECUTED → Not ExecutedWIP → In ProgressPASS → PassFAIL → FailBLOCKED → BlockedCustom → Custom

Default Status Description

As Scale’s configuration

Default Status Color

As Scale’s configuration

Custom Status Description

As Squad’s configuration

Custom Status Color

As Squad’s configuration

Assigned To

Assigned To

Defects

Issues

Comment

Comment

Comment Rich text attachment

Executed By

Executed By

Executed On

Executed On

Total Execution Time

Estimated

Total Logged Time

Actual

Execution Work Flow Status

N/A

Component (In Cycle Summary grid)

Present under Details section

Label (In Cycle Summary grid)

Present under Details section

Attachments

Attachments

Execution History

Not Supported

Test Details

Test Script

Step results Test step

Test Script Test step

Step results Test data

Test Script Test data

Step results Test result

Test Script Test result

Step results Status

Test Script Status

All Test Step Results Statuses - UNEXECUTED, PASS, FAIL, WIP, BLOCKED, Custom

UNEXECUTED → Not ExecutedWIP → In ProgressPASS → PassFAIL → FailBLOCKED → BlockedCustom → Custom

Step results Comments

Test Script Actual Result

Step level Attachments

Test Script attachments

Step level custom fields

Test Script custom fields

Step results attachments

Test Script attachments

Step results defects

Test Script Issues

Execution search filters

N/A

Test execution custom fields

Squad

Scale

Text Field (single line)

A basic single line text box custom field to allow simple text input.

Text Field (Single Line)

Text Field (multi-line)

A multiline text area custom field to allow input of longer text strings.

Text Field (Multi-Line)

Number Field

A custom field that stores and validates numeric (floating point) input.

Number

Radio Buttons

A list of radio buttons.

N/A

Checkboxes

Choose multiple values using checkboxes.

Checkbox

Select List (single choices)

A single select list with a configurable list of options.

Select List (Single Choice)

Select List (multiple choices)

Choose multiple values in a select list.

Select List (Multi-Choice)

Date Picker

A custom field that stores dates and uses a date picker to view them.

Date Picker

Date Time Picker

A custom field that stores dates with a time component.

N/A

Test cycle folder structure

In Squad, a test cycle is created under a fix version. Fix versions can be in released or in unreleased state and the tree structure to organize test cycles are grouped by it. By default, a fix version named Unscheduled and a test cycle named Ad-hoc for each fix versions is present. Test cycles can have one more level called Test folder under it.

In Scale, the folder hierarchy is created first and for each folder test cycles can be created. Folder structure are present for n-levels and fix versions are present as a field for the test cycle.

For migrating data from Squad to Scale, the test cycle and folder hierarcy under the fix versions is migrated as the folder structure in Scale. The executions present for each of these cycles and folders is added by creating a test cycle each under the respective folder node. The test cycle is given a name with the folder name prefix for e.g., login-cycle. The fix version for these test cycles is added as the fix version field value for the test cycle.

Ad hoc test cycles executions is migrated to folder named Ad hoc and by creating multiple test cycles with each fix versions added to it.

API Keys

Squad

Scale

API Tokens

Existing tokens from Squad is not migrated. New api tokens need to be created.

Test Automation

Scale

Squad

Saved configurations

Since the automation in Scale is REST API based, the saved automation configurations won’t be applicable.

Publication date: