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

Linked entity and relationship lists inconsistent in knowledge tab #9531

Closed
Lhorus6 opened this issue Jan 8, 2025 · 0 comments · Fixed by #9870
Closed

Linked entity and relationship lists inconsistent in knowledge tab #9531

Lhorus6 opened this issue Jan 8, 2025 · 0 comments · Fixed by #9870
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)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Jan 8, 2025

Description

When in a Knowledge tab, the list view of relationships and linked entities is inconsistent depending on the relationship and its direction. See example in repro case.

Environment

6.4.5

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a Malware X
  2. Create a Malware Y
  3. Create a Malware Z
  4. Create the relation "Malware X -> variant of -> Malware Y"
  5. Create the relation "Malware Z -> variant of -> Malware X"
  6. Go on Malware X > Knowledge tab > "Variants"
    -> You will see Malware Y and Z listed in the "entities list view" BUT you will see only the relation with Malware Y in the "relationships list view":

Image

Image

Expected Output

If I see two malware in the list, I should have at least two relationships

@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 8, 2025
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 9, 2025
@nino-filigran nino-filigran added this to the Bugs backlog milestone Jan 9, 2025
@delemaf delemaf self-assigned this Jan 30, 2025
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 7, 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)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants