Requirement Traceability Report shows "No Requirements found!" immediately after changing Test Environment, until page is refreshed and report regenerated

Description:

When changing the Test Environment filter in the Requirement Traceability Report and generating the report immediately after, the report incorrectly displays "No Requirements found!", even though requirements exist for the selected scope. The issue only resolves after refreshing the page and generating the report again.

Steps to reproduce:

1. Open the Requirement Traceability Report for a project with existing requirements issues.
2. Set the Scope to anything (ex.: Latest) and generate the report: the requirements load correctly.
   
   
3. Open the report configuration again and change the Test Environment filter.
   
4. Click Apply.
5. Observed: "No Requirements found!" is displayed.
   
6. Refresh the page (observe that the Test Environment change is already saved).
   
7. Generate the report again without changing any further settings.
8. Observed: requirements now load correctly, with statuses reflecting the selected Test Environment.
   

Expected behavior:

The Test Environment filter should only affect which Test Runs are counted when calculating each requirement's status (ex.: pass/fail). It should have no effect on the number of requirement issues returned, as that is determined solely by the Scope setting (Latest / Version / Test Plan).

Actual behavior:

Immediately after changing the Test Environment and generating the report by clicking on Apply, the report returns "No Requirements found!", incorrectly implying no requirements exist for the given scope.