Are Xray Server and Xray Cloud the same product?
No. Besides the change in the architecture, the products also have several differences. Although we try to keep them as close as possible featurewise, they must be understood as two different apps, although with a lot of similarities. Most of these differences result from the architecture since in Cloud, Jira and Xray run and 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.
Please check the major differences in Xray Server vs Xray Cloud
What happens 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 Xray cloud.
Xray Server | Xray Cloud |
|---|---|
Begin Date | Begin Date |
Conditions | |
Cucumber Scenario | Not a custom field. The information is shown in the Test Details panel:
|
Cucumber Test Type | Not a custom field. All Cucumber Types declared as "Cucumber".
|
End Date | End Date |
Test Repository Path | Not a custom field. The information is shown in the Test Details frame:
|
Generic Test Definition | Not a custom field. The information is shown in the Test Details frame, similar to the Cucumber Scenario. |
Manual Test Steps | Not a custom field. The information is shown in the Test Details frame:
|
Pre-Condition Type | |
Pre-Condition association with a Test | |
Requirement Status | |
Revision | Revision |
Steps Count | |
Test Type | |
TestRunStatus | |
Test Plans associated with a Test | |
Test Sets associated with a Test | |
Test Count | |
Tests association with a Pre-Condition | |
Tests associated with a Test Plan | |
Tests association with a Test Set | |
Tests association with a Test Execution | |
Test Environments | |
Test Execution Defects | |
Test Execution Status | |
Test Set Status | |
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