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

Link to relationship object to ObservedData objects in Infrastructure object is wrong #6400

Closed
sweet-mentat opened this issue Mar 21, 2024 · 1 comment · Fixed by #6469
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)
Milestone

Comments

@sweet-mentat
Copy link

Description

In the GUI, when I view an Infrastructure object and click on the Knowledge tab, I can view my timeline of ObservedData objects that have imbedded relationships to the Infrastructure object. When I click on any of the ObservedData objects to view the relationship object, it takes me to the wrong link. It takes me to: (Actual Output)
https://<opencti_domain>/dashboard/threats/intrusion_sets/<infrastructure_object_id>/knowledge/relations/<observed_data_id>
I get an error that states "This page is not found on this OpenCTI application."

When I correct the link to this it works: (Expected Output)
https://<opencti_domain>/dashboard/observations/infrastructures/<infrastructure_object_id>/knowledge/relations/<observed_data_id>
The corrected link takes me to the correct page where I can view the relationship object that relates the Infrastructure object and the ObservedData object.

Environment

  1. OpenCTI docker image, opencti/platform:6.0.5
  2. OpenCTI version: OpenCTI 6.0.5
  3. OpenCTI client: frontend
  4. Other environment details:
@sweet-mentat sweet-mentat added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 21, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 21, 2024
@nino-filigran
Copy link

This behavior is reproduced also on my side.

@SamuelHassine SamuelHassine added this to the Release 6.0.9 milestone Mar 22, 2024
@frapuks frapuks self-assigned this Mar 25, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 26, 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)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants