[go: nahoru, domu]

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

Last created relationship with a relationship displayed as Unknown #6865

Closed
Archidoit opened this issue May 2, 2024 · 3 comments · Fixed by #7472
Closed

Last created relationship with a relationship displayed as Unknown #6865

Archidoit opened this issue May 2, 2024 · 3 comments · Fixed by #7472
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
Archidoit commented May 2, 2024
  • Go to an entity that has a relation with a relationship
  • In the entity overview, in the 'last created relationship', the relationship target is displayed as Unknown :
    image
  • In the Knowledge tab, nothing is displayed in the 'name' column :
    image

When we click on the relationship line :
image

@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 May 2, 2024
@nino-filigran
Copy link

@Archidoit I'm not able to reproduce either on Demo or Testing.
I tried with several entities (Malware, Intrusion Sets, IOCs), going into the entity knowledge tab, creating a relation from there. Going back to the entity overview (went to both each time) and everything was displayed well. Can you let me know where/which case did create this issue for you?

@nino-filigran nino-filigran added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels May 3, 2024
@Archidoit
Copy link
Member Author
Archidoit commented May 3, 2024

Exemple of steps to reproduce: @nino-filigran

  • On the relationships tab, click on a relationship of type 'uses'
  • Add a 'linked entity' of type 'indicator'
  • Go to the indicator overview

@nino-filigran
Copy link

To be clear, about the repro case, please use the "linked entities" as shwon in the screenshot, not the one in the list:
image

I've been able to reproduce. I think there are couple of things going wrong in here:

  • when selecting the + on linked entities, the look and feel is still the "old one": this is not to be fixed here, since it's a feature not a bug
  • when selecting an indicator, the original entity that you want to create appears in an odd way (it looks like we're using a representative), while we should the From Entity exactly like the Target entity
    image
  • when going to the indicator's page, it looks like a relation has been created, but the "to entity" is a relationship type uses instead of an entity (I my case it was supposed to be an intrusion set)
    image
  • when going to the indicator's knowledge tab, the relation does not appear (is it because the relation is not vzalid, since we're creating a relation that points to a relation?
    image
  • when clicking on the relation, same as the begining, it's odd:
    image

@nino-filigran nino-filigran removed the needs more info Intel needed about the use case label May 3, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.11 milestone May 3, 2024
@Jipegien Jipegien added the ui for scope limited to UI change label Jul 1, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jul 3, 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) ui for scope limited to UI change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants