Disabling a Custom Test Status at the Project level shows a global impact warning, even when the status is not used in the selected project

Description: When trying to disable a custom Test Status (e.g., ABORTED) from a specific project (e.g., Guru), the system incorrectly shows a warning that Test Runs will be affected, even though no such Test Runs exist in the Guru Project. The impact is evaluated globally across all projects instead of just the selected one.

Pre-Conditions:

• A custom Test Status (e.g., ABORTED ) is created and enabled across multiple projects
• The Status is actively used in another Project ( e.g., TEJ)
• The same status is not used at all in the project (e.g., GURU)

Steps to Reproduce

• Create a custom Test Status ( e.g., ABORTED ) and enable it across all Projects
• In the project "GURU", do not use the Status.
• In another project, "TEJ", use the Custom status (ABORTED)
• Navigate to the global Test Statuses in the admin settings, try to disable the status from the GURU project only by unchecking it.

• Observe the warning message

Actual Result:

A warning appears stating: "1 Test Run(s) are currently in this status and will be migrated to the status chosen below."

Even though the project "GURU" has no such TestRuns, the warning is shown based on global usage.

Expected Result:

The system should evaluate the usage of the Test status only within the selected project (Guru)

No warning should appear if the status is not used in that project.

Version

• <app versions>

NOTE: The same issue is also observed with the Test Step Statuses. Project-level disabling still triggers a global usage warning, even when the status is not used in the specific project.