Data Transfer
During your upgrade, the Jira settings and permission remain the same. On this page, you can find the migrating fields and its respective mapping details.
Test Cases Fields
During your upgrade, the Jira settings and permission remain the same. On this page, you can find the migrating fields and its respective mapping details.
Squad Test Cases Fields | Scale Test Cases Fields | Description |
|---|---|---|
Summary | Name | The system migrates data from the Squad’s test case Summary field goes to the Name field inside the Scale test case. |
Description | Objective | The data from Squad’s test case Description field goes to the Objective field in Scale’s test case. |
Status | Status | The system extracts the tests case statuses from Jira (To Do, In Progress, Done, and so on) for each project. It uses this data to re-create it as custom statuses for test cases in Scale. Then, it assigns the status accordingly to test cases migrated from Squad to Scale. |
Assignee | No equivalent inside the test case creation in Scale | The system creates a custom field for test case in Scale with a type user picker called Assignee and maps it to Squad's Assignee. |
Labels | Labels | The data from labels of Squad’s test case migrates to Scale’s labels. |
Sprint | No equivalent inside the test case creation in Scale. | The field Sprint from Squad becomes a test case custom field(select list multi-choice) in Scale with the name Sprint that contains Squad’s data. |
Story point estimate | No equivalent inside the test case creation in Scale | The system does not migrate this field. There is no use of story points in Scale. |
Fix versions | No equivalent field inside the test case creation in Scale. | The system migrates Squad’s Fix versions field data to the test case custom field (select list multi-choice) in Scale's Fix versions field. |
Affected versions | No equivalent field inside the test case creation in Scale | If the value exists, the system migrates Affected version field as a custom field called Affected version (select list multi-choice) to Scale’s test case. |
Reporter | Owner | The system migrates Squad's Reporter field data to Scale’s test case Owner field. |
Priority | Priority | Priorities migrate as custom fields. The system assigns the priorities to specific test case. |
Due date | No equivalent field inside the test case creation in Scale | The data from Squad’s Due Date field goes to Scale's custom field with the type Date picker called Due Date. |
Original estimate | Estimated time | The system transform the data into hours and minutes format (hh:mm). If the value is higher than 99h:59m, the system truncates it to 99h:59m. Then, it assigns this value to the Estimated time field in the Scale Test case. |
Time Tracking | No equivalent field inside the test case creation in Scale. | The system does not migrate this field. Time tracking field in Squad’s test case represents the logged time. The field Actual inside Scale’s test player is equivalent to this field. We skip this field for the first version of our upgrade engine. |
Start date | No equivalent field inside the test case creation in Scale | If the value exists, the system migrates Squad’s Start dates field as Start dates custom field to Scale with the type Date picker. |
Environment | No equivalent field inside the test case creation in Scale. | The system creates a custom field in Scale called Environment (type: Text Field (Multi-Line)). It transfers data from Squad’s Environment field to this field in Scale |
Component | Component | If Squad’s Component field contains multiple values, the system maps this component to Scale’s test case custom field called Squad components (type Select List (multi Choice)). |
Epic link | Test case → traceability tab → Issue | The system connects epic link to Jira issue inside the traceability section of the test case. |
Issue links | Test case → traceability tab → Issue | The system connects issue link to Jira issue inside the traceability section of the test case. |
Comments | Comments | The data from Squad's Comments migrate unchanged to Scale’s test case field Comments. |
Attachments | Attachments | Attachments migrate unchanged. |
Subtasks | Test case → traceability tab → Issue | The system connects sub-task link to Jira issue inside the traceability section of the test case. |
Test Case Custom Fields
All of the test case custom fields will be migrated except the one with Jira Advanced type.
The data from Squad's fields gets migrated to Scale's fields as shown in the following table:
Squad Test Custom Fields | Scale Test Custom Fields | Description |
|---|---|---|
Checkboxes | Select List (Multi-Choice) | NA |
Date picker | Date picker | NA |
Date Time picker | Date picker | The system maps the data to the Scale's custom field with the type Date Picker. It removes the time and transfer only the date. |
Labels | Label field inside the test case | NA |
Number field | Number | NA |
Radio Buttons | Select List (Single Choice) | NA |
Select list (cascading) | NA | The system does not migrate the data. |
Select list (multiple choices) | Select list (multiple choices) | NA |
Select list (Single choices) | Select list (Single choices) | NA |
Paragraph (supports rich text) | Text Field (Multi-Line) | NA |
Short text (plain text only) | Text Field (Single-Line) | NA |
URL Field | Text Field (Multi-Line) | NA |
User Picker (single user) | User Picker | NA |
Test Case Linked Issues
The system extracts linked issues from the Squad test case and links them to the Scale test case in the traceability section.
Test Case Web Links
The system extracts weblinks linked to a Squad test case and links them to the Scale test case in the traceability section.
Test Case Steps
The system migrates all the test case custom fields except the one with Jira Advanced type
Squad Test Case Step | Scale Test Case Step |
|---|---|
Test Step | Step |
Test Data | Test Data |
Test Result | Expected Result |
Attachments | Attachments |
Custom Fields | Custom Field |
Test Case Step Attachments
We migrate test case step attachments as they are.
Test Case Step Custom Field
The Test Case Step Custom fields that gets migrated from Squad to Scale are enlisted here:
Squad Test Case Step | Scale Test Case Step | Description |
|---|---|---|
Text Field (single line) | Text Field | The system maps Squad's field to Scale’s custom field with the type Text Field (Single Line). |
Text Field (single line) A basic single line text box custom field to allow simple text input. | Text Field | The system maps Squad's field to Scale’s custom field with the type 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) | The system maps Squad's field to Scale’s custom field with the type Text Field (Multi-Line). |
Number Field A custom field that stores and validates numeric (floating point) input. | Number | The system maps Squad's field to Scale’s custom field with the type Number. |
Radio Buttons A list of radio buttons. | NA | The system maps Squad's field to the Scale’s custom field with the type Select List (Single Choice). |
Checkboxes Choose multiple values using checkboxes. | Checkbox | The system maps Squad's field to the Scale’s custom field with the type Select List (Multi-Choice). |
Select List (single choices) A single select list with a configurable list of options. | Select List (Single Choice) | The system maps Squad's field to the Scale’s custom field with the type Select List (Single Choice). |
Select List (multiple choices) Choose multiple values in a select list. | Select List (Multi-Choice) | The system maps Squad's field to the Scale’s custom field with the type Select List (Multi-Choice). |
Date Picker A custom field that stores dates and uses a date picker to view them. | Date Picker | The system maps Squad's field to the Scale’s custom field with the type Date Picker. |
Date Time Picker A custom field that stores dates dates with a time component. | NA | The system maps Squad's field to the Scale’s custom field with the type Date Picker. It removes the time and transfer only the date. |
Test Case Change History
To migrate Squad test case history to Scale, the system combines data from the Jira issue history and the Test Details History tab.
From the Test Details History tab, the system fetches data about the changes made to Squad test steps.
From the Jira Issue History tab, the system fetches the available data.
After getting the data from both Squad histories, the system sorts it based on the time a change was made (sort by date and time to get the right order). Once the data is sorted, the system imports it to Scale as a separate change event to the test case.
Test Cases Fields
The data from Squad's fields gets migrated to Scale's fields as shown in the following table:
Squad Test Case Fields | Scale Test Case Fields | Description |
|---|---|---|
Summary | Name | The system migrates data from the Squad’s test case Summary field goes to the Name field inside the Scale test case. |
Description | Objective | The data from Squad’s test case Description field goes to the Objective field in Scale’s test case. |
Status | Status | The system extracts the tests case statuses from Jira (To Do, In Progress, Done, and so on) for each project. It uses this data to re-create it as custom statuses for test cases in Scale. Then, it assigns the status accordingly to test cases migrated from Squad to Scale. |
Assignee | No equivalent inside the test case creation in Scale | The system creates a custom field for test case in Scale with a type user picker called Assignee and maps it to Squad's Assignee. |
Labels | Labels | The data from labels of Squad’s test case migrates to Scale’s labels. |