---
title: "[Xray Server] Wrong Execution Result is taken over to Requirement Status"
canonical: "https://docs.getxray.app/space/ProductKB/46269120/%5BXray%20Server%5D%20Wrong%20Execution%20Result%20is%20taken%20over%20to%20Requirement%20Status"
format: markdown
---
## **Problem**

<span style="color: #172b4d">Although the last run of a Test was passed, the Requirement Status of the linked issue is not taking the latest execution result:</span>

![image](media://751a40a2-19e6-40ea-a5ed-4dcbc81a075b)

![image](media://1c654bbd-27a0-4ba3-affb-52050ec60673)


## **Possible Causes**

Xray has a Tool called **Final statuses have precedence over non-final statuses; when** it is <u>Unchecked,</u> the Latest Test Run Status Calculation will always consider the ***Latest Created*** Test Run.

Now, a Test Run is only created when a Test is associated with a Test Execution.  
   
In the provided example, the Test Execution with the key **680[PASS]** was created after **669[FAIL]**, but the Test Execution **680[PASS]** was associated with the Test before the **669[FAIL]**, so the latest Test Run is from** 669[FAIL]**.


The mentioned option is in Jira Administration → Manage apps → Xray -> Manage Test Statuses:

![image](media://b6e8977f-cbc2-4097-a119-5c3889f3451e)


# Link for related documentation

[*Final statuses have precedence over non-final statuses*](https://getxraydocs.atlassian.net/wiki/display/XRAY/Manage+Test+Statuses#ManageTestStatuses-Finalstatuseshaveprecedenceovernon-finalstatuses)