Problem Description

When a Playbook is configured to be restricted to a specific Work Item, such as Incident, the Playbook details page displays that it is available for All Request Types. In reality, it applies only apply to the Request Types associated with the selected Work Item. The correct Request Types are only shown when an explicit restriction is applied at the Request Type level. This mismatch can lead to confusion and makes it difficult to accurately understand which Playbooks are configured for which Request Types, potentially impacting configuration transparency and maintenance.

Suggested Resolution

When setting a condition to display Playbooks based on a specific Work Type, such as "Incident," only the Request Types associated with that Work Type should appear in the Playbook details section.

Why this is important?

This creates confusion for users trying to identify which Playbooks are configured for specific Request Types, as the Playbook details section displays "All Request Types" instead of only those tied to the selected Work Item Type. Accurately reflecting the associated Request Types is important for filtering them and ensuring that the correct Playbooks are triggered for the right scenarios.

Workaround (if any)

NA