How to reset the 'TestRunStatus' field values that are not synchonized with the real 'Test Execution' status ?

Question

Hi there,

My XRay is in 2.0.3 version, 'Final statuses have precedence over non-final statuses' is not activated and 'Test Run Status Custom Field Version' is set to 'No Version'

My problem is that, since we've updated from v1 to v2 (10th of October), some of the projects are experiencing problems with their TestRunStatuses... The last TestRunStatus is still the one from the v1 !

You can see the results in this pic :

TestRunStatus_vs_TestExecutionResults.jpg

In the left, we see the result from a jql search in whitch we'd must have the last executed test run status, that are actually all PASS...

Here's what I've tried on another JIRA platform (copy from prod), without any success :

* Reindex... Mutiple times
* Activate / Deactivate 'Final statuses have precedence over non-final statuses'
* Integrity Checker for ALL... Multiple times
* Clear Test Run Status Custom Field for only 1 test withissue menu, and reindex
* Clear Test Run Status Custom Field for the 4 precited tests with bulk change, and reindex
* Clear Test Run Status Custom Field for ALL the tests with admin module, and reindex
* Upgrade from 2.0.2 to 2.0.3 (I saw this fix so I tried : XRAY-1130)

I've no more idea. Can you help me ?

Is it a bug ?

In this case, will it be fix and when ?

Thanks in advance !

VM

TestRunStatus_vs_TestExecutionResults.jpg

Anju Patel_7gl9yt · Answer

Dear Team,
i need to know how should i test Integrity Checker in xray jira?
as of now i have got access to modify the checkboex in admin console.

Bruno Conde · Answer

Hi Vincent,

Just to clarify, the TestRunStatus value can be invalid only in certain corner cases. This is why we provide these integrity check actions.

Even if the custom field value is invalid, reseting the value should immediately update the custom field with the correct value. Because you already performed these reset actions, the problem must be in the calculation itself.

Best Regards,

Bruno Conde.

Vincent MASSIP · Answer

Hi Bruno and thank you.

Actualy, we don't use the 'Test Environments' field...

But I saw this in the 'Integrity Checker' documentation :

Starting from version 2.0.0 of Xray for JIRA, the following Xray custom fields are calculated upon any change. This means the value for the custom fields is stored instead of calculated on the fly. This improves performance considerably for several Xray screens and queries.

/[...]

Despite our best effort, there might be certain use cases where the custom fields are not updated, resulting in out of date values. When this happens we provide the ability to remove the value of all custom fields in this page. The value will then be calculated upon fist access, or when a JIRA re-index operation is performed.

I've done a full clear TestRunStatus cache and a full JIRA reindex... Same result...

I'll log a ticket to your support.

Thank you.

Best regards.

VM