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

Impossible to create a relationship from an entity "knowledge" view #6343

Closed
Lhorus6 opened this issue Mar 13, 2024 · 0 comments · Fixed by #6367
Closed

Impossible to create a relationship from an entity "knowledge" view #6343

Lhorus6 opened this issue Mar 13, 2024 · 0 comments · Fixed by #6367
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Mar 13, 2024

Description

From an entity, we can no longer create a relationship from the "knowledge" view, as the "+" no longer works. When clicked, the side panel no longer opens.

This bug seems to be present on ALL entity types (threat, arsenal, etc.).

Environment

OCTI 6.0.5

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Navigate on an entity "Threat actor group"
  2. Go on the knowledge tab
  3. Go on victimology
  4. Try to create a relation by clicking on the "+" in the bottom right corner
@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 Mar 13, 2024
@nino-filigran nino-filigran added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 14, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.7 milestone Mar 14, 2024
@SarahBocognano SarahBocognano self-assigned this Mar 14, 2024
@Kedae Kedae closed this as completed Mar 14, 2024
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 14, 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 critical use to identify critical bug to fix ASAP 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.

5 participants