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

Sighting details are empty in investigation graphs #4086

Closed
Archidoit opened this issue Aug 17, 2023 · 0 comments · Fixed by #4091
Closed

Sighting details are empty in investigation graphs #4086

Archidoit opened this issue Aug 17, 2023 · 0 comments · Fixed by #4091
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)

Comments

@Archidoit
Copy link
Member

Archidoit commented Aug 17, 2023

Description

Sighting details are empty in investigation graphs.
Same for ref relationships

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  • Go to an investigation graph.
  • Click on a sighting relationship (arrow).
  • The preview window is empty.

image

Expected output

Display the sighting details, like it is done for other relationships.

Other bugs resolved in this issue

  • In an investigation graph, click on a ref (label/making etc), then click on the edit button in the toolbar, an error occurs.
  • same when trying to edit a sighting
    Comment: to see refs objects in such graph, you can follow these steps:
    add an entity that has refs in an investigation graph, click on the entity, click on the 'expand' button of the toolbar
@Archidoit Archidoit added the bug use for describing something not working as expected label Aug 17, 2023
@Archidoit Archidoit self-assigned this Aug 17, 2023
@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 21, 2023
SamuelHassine pushed a commit that referenced this issue Aug 22, 2023
…igation graphs (#4086)

Co-authored-by: Romuald Lemesle <romuald.lemesle@filigran.io>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 22, 2023
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
2 participants