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

[Playbook] Modify severity field with playbooks #7648

Closed
Lhorus6 opened this issue Jul 9, 2024 · 0 comments
Closed

[Playbook] Modify severity field with playbooks #7648

Lhorus6 opened this issue Jul 9, 2024 · 0 comments
Assignees
Labels
feature use for describing a new feature to develop playbook Linked to automation engine solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Jul 9, 2024

Use case

Need to modify the severity fields of my Incident based on label that my source is using

Current Workaround

Manual work

Proposed Solution

Add the possibility in the "Manipulate knowledge" component

image

If the feature request is approved, would you be willing to submit a PR?

No

cc @romain-filigran

@Lhorus6 Lhorus6 added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jul 9, 2024
@romain-filigran romain-filigran added playbook Linked to automation engine and removed needs triage use to identify issue needing triage from Filigran Product team labels Jul 15, 2024
@romain-filigran romain-filigran added this to the Release 6.5.0 milestone Jul 15, 2024
@nino-filigran nino-filigran self-assigned this Dec 11, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop playbook Linked to automation engine 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

5 participants