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] Changing the score on indicator does not work #5745

Closed
Lhorus6 opened this issue Jan 30, 2024 · 0 comments
Closed

[Playbooks] Changing the score on indicator does not work #5745

Lhorus6 opened this issue Jan 30, 2024 · 0 comments
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Lhorus6
Copy link

Lhorus6 commented Jan 30, 2024

Description

When I try to modify the score on indicator, the playbook executes correctly and the execution logs are good, but the score is not modified in the end (see playbook config).

Environment

OCTI 5.12.25

Reproducible Steps

  1. Create a playbooks
  2. Add a listener on Creation and Modification with filter : "Entity type = Indicator" AND "Label = test"
  3. Add a manipulate component that : "Replace -> Score -> 91"
  4. Add the send to ingestion component

NB: a playbook named "Issue/5745" is available on the testing platform

Expected Output

To have my indicators with the label "test" with a score of 91

Actual Output

No change on score despite correct playbook execution logs

Screenshots

Playbook

Screenshot 2024-01-30 110954

Listener

Screenshot 2024-01-30 110958

Manipulate

Screenshot 2024-01-30 110950

Execution logs

Screenshot 2024-01-30 111214

Send for ingestion log (corect but not applied when I return on the indicator)

Screenshot 2024-01-30 111222

@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 Jan 30, 2024
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 30, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.26 milestone Jan 30, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 30, 2024
@SamuelHassine SamuelHassine self-assigned this Jan 30, 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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants