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

No action at 'no label' chip click in indicators list of Knowledge view #9816

Closed
Archidoit opened this issue Feb 4, 2025 · 2 comments
Closed
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) ui for scope limited to UI change
Milestone

Comments

@Archidoit
Copy link
Member

Description

No action at 'no label' chip click in indicators list of Knowledge view, whereas it should add a 'label is empty' filter

Reproducible Steps

  • Go to a malware (or any other entity)
  • Go to the knowledge tab
  • Go under the 'Indicator' section
  • Click on a 'no label' chip in an indicator line

Image

Actual behavior

Nothing happens

Expected behavior

A filter 'label is empty' is added (as it is the case for the other entity types in the Knowledge tab)

@Archidoit Archidoit added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 4, 2025
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 6, 2025
@romain-filigran
Copy link
Member

This seems to be the case for all indicator views. Must be fixed everywhere

@romain-filigran romain-filigran added the ui for scope limited to UI change label Feb 6, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Feb 6, 2025
@Gwendoline-FAVRE-FELIX
Copy link
Member

Related to : #9292

@Gwendoline-FAVRE-FELIX Gwendoline-FAVRE-FELIX self-assigned this Feb 6, 2025
@labo-flg labo-flg modified the milestones: Bugs backlog, Release 6.5.2 Feb 17, 2025
@labo-flg labo-flg added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 17, 2025
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) ui for scope limited to UI change
Projects
None yet
Development

No branches or pull requests

5 participants