Skip to content

[Playbook] Manual Playbook trigger ignores Playbook filters #13856

@Lhorus6

Description

@Lhorus6

Description

When a Playbook is configured to be triggered manually, the filters defined on the Playbook are not respected. I.e. Playbooks are proposed even when the triggering entity does not match the Playbook’s filter criteria.

Environment

OCTI 6.9.4

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a Playbook with a Manual component as the trigger with the filters such as: Entity Type = "Report" AND Label = "testing-purposes"
Image
  1. Go to a Report entity without the label "testing-purposes".
  2. Click “Enroll in Playbook” on this Report.

Expected Output

The Playbook should not be listed as an available option, since the triggering Report does not match the Playbook filters (missing the required label).

Actual Output

The Playbook is listed and can be executed, even though the Report does not satisfy the Playbook’s filter conditions.

Additional information

Impact : Makes Playbook filtering unreliable for manual execution and can lead to Playbooks being executed on unintended entities

Metadata

Metadata

Assignees

Labels

buguse for describing something not working as expectedenterprise editionuse to identify feature part of the Enterprise Edition licenceplaybookLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions