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

[File indexing] Jumping on an external ref linked to a file doesn't work #6943

Closed
Lhorus6 opened this issue May 13, 2024 · 0 comments · Fixed by #7254
Closed

[File indexing] Jumping on an external ref linked to a file doesn't work #6943

Lhorus6 opened this issue May 13, 2024 · 0 comments · Fixed by #7254
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

Comments

@Lhorus6
Copy link

Lhorus6 commented May 13, 2024

Description

When I click at the end of the line to be redirected to the object containing my file, it doesn't work if it's an external ref.

Environment

OCTI 6.1.0

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a Report with an external ref
  2. Run the "import ext ref" enrichment connector to generate a pdf
  3. In the global search bar, look for the filename of the file generated in step two.
  4. You'll find it in the “Files search” tab, clicked at the end of the line to jump on the ext ref.

Screenshot 2024-05-13 161938

-> doesn't work. After clicking at the end of the line:

Screenshot 2024-05-13 162413

@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 May 13, 2024
@SamuelHassine SamuelHassine added this to the Bugs backlog milestone May 13, 2024
@nino-filigran nino-filigran added needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels May 14, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label May 15, 2024
@Kedae Kedae self-assigned this Jun 6, 2024
@Kedae Kedae modified the milestones: Bugs backlog, Release 6.2.0 Jun 6, 2024
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 7, 2024
daimyo007 pushed a commit to fbicyber/opencti__opencti that referenced this issue Jun 24, 2024
@Jipegien Jipegien added the ui for scope limited to UI change label Jul 1, 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.

6 participants