Problem:

When performing a migration from Server/DC to Cloud using the Jira Cloud Migration Assistance, you will find some logs mentioning that some custom fields from Xray can’t be converted to the Cloud. (like the example below)

2024-01-14 15:08:28,150+0100 ParallelIssueExporter-Thread-13500-114754 WARN      [c.a.j.m.e.core.issue.CloudChangeItemConverter] CustomField Type com.xpandit.plugins.xray:test-repository-path-custom-field on Issue TEST-103 can't be converted to cloud change item
2024-01-14 15:02:22,151+0100 ParallelIssueExporter-Thread-13500-114754 WARN      [c.a.j.m.e.core.issue.CloudChangeItemConverter] CustomField Type com.xpandit.plugins.xray:test-repository-path-custom-field on Issue TEST-123 can't be converted to cloud change item
2024-01-14 15:02:22,151+0100 ParallelIssueExporter-Thread-13500-114754 WARN      [c.a.j.m.e.core.issue.CloudChangeItemConverter] CustomField Type com.xpandit.plugins.xray:test-repository-path-custom-field on Issue TEST-123 can't be converted to cloud change item

Causes:

Those and all the other warm messages regarding the custom fields should not be a problem, since most of the Xray custom fields (Server) are, indeed, not converted into Cloud Custom Fields; in fact, we have only a handful of custom fields in the Cloud with the rest of the information going into internal Xray entities.

Some of the custom fields available in the Server are not displayed in the Cloud as custom fields. This Sever data has been moved to a tab. So, all the Xray custom fields that used to appear on the issue creation screen will be displayed after you create the test. Therefore, all the Xray native custom fields are migrated and have their value-added on the Xray Cloud side.   For example, the Manual Test will not have a custom field in the Cloud. But, its value will show in the Test Details tab:


Besides that, we wanted to take a moment to clarify some information about Xray for Jira Cloud. While Xray for Jira Cloud is an offshoot of the highly successful Xray for Jira Server, the architecture that supports both products is different. As a result, there will be some differences between the two apps, although there are many similarities.

Most of these differences are related to the architecture since, in Jira Cloud, all Apps (including Xray) run on different hosts. Xray Cloud communicates with Jira Cloud exclusively through its API, which can affect all aspects of the products. 

If a feature is not supported by the API, it is not possible to make it available in Xray Cloud. For more information, please check Xray Server and Xray Cloud, Xray- Server-Cloud migration, and what to expect!.



 

 

 

 

 

 

  • No labels