Synchronize XRAY status with Jira Status

[Bogdan Gorka]

XRAY has its own calculated status field for Tests, Test Executions and Test Plans. They are displayed on an issue screen, but they are not Jira custom fields.

Is it possible to map or synchronize XRAY statuses with the Jira statuses? ScriptRunner maybe?

[Rogério Paiva - Xray Xporter · Accepted solution]

Hi @Bogdan Gorka 

In Xray, there are few actions that can be automated based on the Xray status, please check this documentation page (https://docs.getxray.app/display/XRAY/Using+Jira+workflows+for+testing+purposes):

• Disallow executions of Tests with workflow statuses
• Disallow executions with workflow statuses
  • For Test Executions in specific status
• Set the "In progress Test Execution workflow status"
  • After the first run (i.e., after one the Test Runs in that Test Execution has run)
• Set the "Resolved Test Execution workflow status"
  • When all runs are in final status  (i.e., after all Test Runs that in that Test Execution have been run and have a final status)
• Set the Resolution for Resolved Test Execution, when the "Resolved Test Execution workflow status" is set

Since some status are also custom fields, it could be possible to program some additional actions using other Apps.

Kind regards,
Rogério Paiva [Xray Support Team] 

[Bogdan Gorka]

Thank you @Rogério Paiva - Xray Xporter

Only recently I discovered that the Server/DC XRAY version offers this functionality but the Cloud version not yet.

[Rogério Paiva - Xray Xporter]

You are most welcome @Bogdan Gorka 

There are some differences between Server/DC and Cloud since the architectures are different. In Server/DC architecture Xray is installed in the same host as Jira so that Xray can integrate more easily with Jira. In Cloud, Jira and Xray are in different servers, so the integration is not so easy, and some features that you found in Server/DC are impossible to have in Cloud.

Basically, Xray Server and Xray Cloud are two different apps using different technology. Although we try to keep them as close as possible, it is not always feasible to have the exact same features on both.