Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Playbooks] Incorrect score filter #6094

Closed
Lhorus6 opened this issue Feb 23, 2024 · 0 comments · Fixed by #6096
Closed

[Playbooks] Incorrect score filter #6094

Lhorus6 opened this issue Feb 23, 2024 · 0 comments · Fixed by #6096
Assignees
Labels
bug use for describing something not working as expected filters temporarily used to identify filter issue to facilitate filter team’s work identification solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Feb 23, 2024

Description

When I try to add a filter on scores, the filter is always "=" no matter if I choose "greater than", "lower than or equal", ...

Environment

OCTI 5.12.32

Filigran prod instance

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create playbooks
  2. Add a Listener
  3. Add a component "Filter knowledge" and try to use the filter on "score"
    -> You'll see that you'll only get strict "=" filters.
@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 23, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 23, 2024
@nino-filigran nino-filigran added this to the Release 6.0.0 milestone Feb 23, 2024
@Archidoit Archidoit added the filters temporarily used to identify filter issue to facilitate filter team’s work identification label Feb 23, 2024
@Archidoit Archidoit self-assigned this Feb 23, 2024
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filters temporarily used to identify filter issue to facilitate filter team’s work identification solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants