"When you need to have one Requirement as OK for your client but for your team it still needs to be NOK"
If this is the behaviour that you want, you can do this using Separation of Concerns.
When this option is checked, the result of a Test will affect all Requirements that are associated with it. Uncheck this option if a single Test result affects multiple Requirements in different ways and these might have different statuses depending on specific steps. This will allow you to manually set the affected Requirement statuses for each Test Run on the execution screen. The calculation of the Requirement Status will then consider these Requirement statuses explicitly.
Example:
After creating 2 Requirements: A and B, they are linked to one Test only and set the linking between them as "tests", as shown on the following picture:
Then a Test Execution is created and in the Execution details page you will be able to choose the Status of each Requirement, like on the following screenshot:
If you go to the Requirement A, you have the following Requirement Status:
If you go to the Requirement B, you have the following Requirement Status:
To change this configuration you need to:
| This is a global configuration, so changing this option will affect every projects that you have. |
Requirements Coverage#SeparationofConcerns
Understanding coverage and the calculation of Test and requirement statuses