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.

Sign up for GitHub

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

Jump to bottom

Intrusion-Set Description cannot be updated #5729

Closed
MalwareCantFly opened this issue Jan 28, 2024 · 0 comments
Closed

Intrusion-Set Description cannot be updated #5729

MalwareCantFly opened this issue Jan 28, 2024 · 0 comments
Assignees
@SamuelHassine
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)
Milestone
Release 5.12.24

Comments

@MalwareCantFly
Copy link

Description

Hi,
In the latest version 5.12.23 (community edition), Intrusion-Set's "Description" cannot be updated.
Other functions like updating and Intrusions-Set's "Goals" or "Last Seen" - do work.

Environment

5.12.23 (community edition)

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Enter some Intrusion-Set
  2. Click on the edit button.
  3. Try changing the content of the Description field.
  4. The Direct Update and Update buttons will turn on.
  5. Both of them do not update the Description content.

Screenshots

image
@MalwareCantFly MalwareCantFly added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 28, 2024
@SamuelHassine SamuelHassine self-assigned this Jan 28, 2024
@SamuelHassine SamuelHassine removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 28, 2024
SamuelHassine added a commit that referenced this issue Jan 28, 2024
@SamuelHassine
[frontend] Fix intrusion set edition when using enforce references (#…
c402bc6 
…5729)
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 28, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.24 milestone Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

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
Milestone
Release 5.12.24
Development

No branches or pull requests
2 participants
@SamuelHassine @MalwareCantFly