Significant delay when seeing the pop up button "Add Tests" - Tests associated with Test Execution but not with Test plan.

Description - 

When a Test Execution is associated with a Test Plan that has no Dynamic Filter configured, testsFilterId resolves to null. Without a check to filter out null or missing filter IDs, the API request drops the id parameter entirely (/rest/api/2/filter/search). Consequently, Jira attempts to fetch and paginate through all filters accessible to the user across hundreds of sequential API calls, causing the missing tests warning banner and "Add Tests" button to take around 10 minutes to load.

Pre-conditions - 

• A Jira tenant exists with a large number of accessible shared filters (e.g., following a Data Center migration).

• A Test Plan exists without any Dynamic Filters configured (testsFilterId is null).

• A Test Execution containing Tests not yet in the Test Plan is associated with that Test Plan.

Actual results - 

The client-side code sends thousands of paginated requests to /rest/api/2/filter/search without an id parameter, resulting in a delay of up to 10 minutes before the "missing tests" warning banner and "Add Tests" button appear.

Expected results - 

The code checks for valid filter IDs before making the API request. If no valid testsFilterId exists, the filter search API call is skipped, and the "missing tests" warning banner and "Add Tests" button render immediately.

Version - 

16.25.0

Workaround - 

-