Page History

...

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. 

• Option Separation of Concerns Unchecked
  when this option is unchecked, if your Test is associated with more than one Requirement, you are able to choose the status of each Requirement individually. 
  Imagine you have the Requirement A and Requirement B associated with one Test. On the Execution level you are able to define that the Requirement A is OK and Requirement B NOK.

             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:

• Image Modified

           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:

          Image Modified

            If you go to the Requirement A, you have the following Requirement Status:

         Image Modified

           If you go to the Requirement B, you have the following Requirement Status:

          Image Modified 4

• Option Separation of Concerns Checked
  The result of your Test will affect globally all the Requirements that are associated with it, so if on the Execution page you set the status as PASS, all the Requirements associated will be OK too.

...

1. Go to Jira Administration >> Manage AppsAdd-ons
2. Xray >> Requirement coverage
3. Check or uncheck the option

...

Related articles

Requirements Coverage#SeparationofConcernsCoverage

Understanding coverage and the calculation of Test and requirement statuses

...