Standardize the Disallow executions settings under Miscellaneous to match Data Center behavior, and logic

Description

The "Disallow executions" settings under Miscellaneous in Cloud do not mirror the enforcement, validation, and functional logic used in Data Center. Cloud prevents tests from being added to a test execution entirely, whereas Data Center allows tests to be added but restricts their execution. These options should be updated to operate identically across both environments.

User friction

Inconsistent behavior between Cloud and Data Center creates confusion for administrators, disrupts established workflows, and leads to misaligned expectations regarding execution permissions.

Steps to reproduce (right now) / Actual Result:

• Navigate to Miscellaneous
• Add a status under Disallow executions of Tests with workflow statuses and Disallow executions with workflow statuses
• Open a Test Execution and attempt to add a Test carrying one of the selected statuses

Actual Result: The notification "No new Tests were added to the Test Execution" appears, completely blocking the test from being added
Expected (Data Center) Result: Tests can be added to the Test Execution, but running/executing them is blocked.

IMPACT

What would improve if solved:

• Achieves complete functional parity between Cloud and Data Center
• Restores the ability to assemble test executions without triggering unauthorized runs
• Reduces administrative overhead and eliminates setup confusion

Impact on stakeholders:

• Experience predictable, uniform configuration management and consistent test planning workflows across environments.

Current workaround:

The only possible workaround is to remove the status from the options mentioned above.

CONTEXT & EXAMPLES:

Concrete example:

• Users managing a Test in Cloud cannot pre-stage Tests with specific workflow statuses into a Test Execution container for upcoming cycles, forcing them to modify global permission rules just to organize their test plans.

Workaround risk:

• Not having the same behavior in both Data Center and Cloud may incur confusion and mistakes, since the behavior is expected to be the same.