Issue Summary

When a request type configured in an Playbook filter is deleted, the Playbook filter in the UI automatically displays Request type → Any request type. However, the backend retains the association with the deleted request type ID. As a result, the playbook fails to appear on any tickets, contrary to what the UI indicates.

Steps to Reproduce

1. Navigate to Space Settings > Playbooks and create/configure a playbook with a filter set to a specific request type (e.g., Request type → Sample Request Type 1).

1. Navigate to Space Settings > Request types and delete Sample Request Type 1.

1. Open the playbook configuration again and observe the filter settings in the UI.

1. Create a new issue/request in the project to check if the playbook appears.

Expected Results

• The playbook configuration should indicate that the associated request type was deleted (e.g., show a validation warning/error banner or flag the missing request type).

• If automatically reset to "Any request type", the backend association should be completely cleared so that the playbook properly appear on any ticket.

Actual Results

• The UI resets the filter display to Request type → Any request type, giving the false impression that it applies globally.

• In the backend, the playbook remains bound to the deleted request type ID, causing the playbook not to appear  on any tickets.

Workaround

To clear the stale backend reference:

1. Open the affected playbook.

1. Edit the filter: change Request type from Any request type to any existing valid request type.

1. Change the Request type filter back to Any request type  and save the playbook.