Page History
| Table of Contents |
|---|
Are Xray Server and Xray Cloud the same product?
No. Besides the change in the architecture, the products also have several differences. Although , they are two different products with distinct roadmaps and different release cycles. The architecture that supports both products is different, so it affects all aspects of the products. Although we try to keep them as close as possible, featurewise, they must be understood as two different apps, although with a lot of many similarities. Most of these differences result from the architecture since, in Jira Cloud, Jira and Xray run and all Apps (including Xray) run in different hosts. So Xray Cloud communicates with Jira Cloud through its API, and if there is no API that supports a given feature, it is not possible to make it available in Xray Cloud. Other differences may also result from customer feedback and technical decisions. When moving from Server to Cloud. , it is important to be aware of the differences.
Please check the major differences in Xray Server vs. Xray Cloud
What happens to Xray Server custom fields?
Being a different App, Xray Cloud has a different approach to custom fields. Most information found in a custom field on Xray Server is now found in other locations on the Xray cloud.
Xray Server | Xray Cloud |
|---|---|
Begin Date | Begin Date (Custom Field) |
Conditions | Not a custom field. The information is shown in the Precondition Details tab:
|
Cucumber Scenario | Not a custom field. The information is shown in the Test Details |
tab:
| |
Cucumber Test Type | Not |
available. All Cucumber Types are declared as "Cucumber" Test Type. |
|
End Date | End Date (Custom Field) |
Test Repository Path | Not a custom field. The information is shown in the Test Details |
tab:
| |
Generic Test Definition | Not a custom field. The information is shown in the Test Details |
tab (similar to the Cucumber Scenario). | |
Manual Test Steps | Not a custom field. The information is shown in the Test Details |
tab:
| |
Pre-Condition Type | Not a custom field. The information is shown in the Precondition Details tab:
|
Pre-Condition association with a Test | Not a custom field. The information is shown in the Test's Precondition tab:
|
Requirement Status | Not a custom field. The information is shown in the Test Coverage tab:
|
Revision |
Revision (Custom Field) | |
Steps Count | N/A |
Test Type | Not a custom field. The information is shown in the Test Details tab:
|
TestRunStatus | Not a custom field. The information is shown in the right-side panel of the Test by pressing the Open Test Status:
|
Test Plans associated with a Test | Not a custom field. The information is shown in the Test's Test Plan tab (similar to Pre-Condition association with a Test). |
Test Sets associated with a Test | Not a custom field. The information is shown in the Test's Test Sets tab (similar to Pre-Condition association with a Test). |
Test Count | N/A |
Tests association with a Pre-Condition | Not a custom field. The information is shown in the Precondition's Test tab. |
Tests associated with a Test Plan | Not a custom field. The information is shown in the Test Plan's Test tab. |
Tests association with a Test Set | Not a custom field. The information is shown in the Test Set's Test tab. |
Tests association with a Test Execution | Not a custom field. The information is shown in the Precondition's Test tab. |
Test Environments | Not a custom field. The information is shown in the right-side panel of the Test Execution:
|
Test Execution Defects | Not a custom field. The information is shown in the Test Execution List report. |
Test Execution Status | Not a custom field. The information is shown in the reports or the Test Execution issue:
|
Test Set Status | N/A |
Test Plan Status |
kb migration
xray cloud X xray server
-> custom fields (don't exist for xray)
-> jira custom fields need to be addressed with atlassian
-> check migration status
...
Not a custom field. The information is shown in the reports or the Test Plan issue:
|
Note: Any other custom field that is not on this list needs to be addressed with Atlassian of the respective product vendor.
Where to check the migration status?
You can check the status of the migration in the Jira Administration \ Apps, on Xray settings:
And check the details:
| Info |
|---|
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...