-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
buguse for describing something not working as expecteduse for describing something not working as expectedenterprise editionuse to identify feature part of the Enterprise Edition licenceuse to identify feature part of the Enterprise Edition licenceplaybookLinked to automation engineLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Description
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:
- Create a Playbook with a Manual component as the trigger with the filters such as: Entity Type = "Report" AND Label = "testing-purposes"
- Go to a Report entity without the label "testing-purposes".
- 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 expecteduse for describing something not working as expectedenterprise editionuse to identify feature part of the Enterprise Edition licenceuse to identify feature part of the Enterprise Edition licenceplaybookLinked to automation engineLinked to automation enginesolveduse to identify issue that has been solved (must be linked to the solving PR)use to identify issue that has been solved (must be linked to the solving PR)