Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Requirement Status does not match

NA March 21, 2019

Hello,

I have done the following tasks:

  • Create a user story (requirement 03)  in a project (BE) with the fix versions are BE-V-01, BE-V-02,  the component BE-C01 
  • Create 4 test issues in an other project (BT) linked to requirement 03
  • In project BT, create a test plan with 2 test execution that contains the all 4 test issues.
  • Exec all tests in the test executions.

However, when I view the user story (see the below image), I found that:

  1. The requirement status is always NOTRUN
  2.  I don't knows where is the value "bs-auth-1.0-rafiki" come from.

2019-03-21 17_27_40-[BE-1308] Requirement 03 - Jira.png

I hope to see some thing like  BE-V-01-OK,  BE-V-02-NOK.

Could some one explain it to me?

In the case that the requirement issues and test issues are in the difference project, how can I organize the fix-version?

Thanks you very much

Best regards,

1 answer

1 accepted

0 votes
Answer accepted
Inês Silva
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 11, 2019

Hi Ngoc,

This issue seems to be related with the strategy used, to calculate the Requirement Status Custom field.
According the request description, seems like "you/customer" want to calculate the Requirement Status based on all the assigned Fix Versions. To achieve that you have to go to Jira Administration -> Add-ons -> Xray - Custom Fields and for the Requirement Status Custom Field Version, you should change to the option "Assigned Versions".
More details on our documentation, here.

Thank you,

Xray Team

NA April 12, 2019

Thanks Inês Silva,

It works now.

Best regards

Like Keerthana Rajasekar likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events