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

The ImportDocument connector doesn't work when importing document from a "Data" tab #6121

Closed
Lhorus6 opened this issue Feb 26, 2024 · 2 comments
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 Feb 26, 2024

Description

When I import a document into an entity (which is not a container!), a bug occurs. There seems to be a problem in creating a relationship (see the screenshot).

NB:

  • I tested in the global import panel or in the Data tab of a container -> no bug
  • I tested on Threat actor and Incident -> bug occurs

Environment

OCTI 5.12.33

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create an Incident
  2. Navigate to the Data tab of the incident
  3. Import a pdf and let the ImportDocument connector do its jobs
    -> You will have an error

Screenshots

Screenshot 2024-02-26 161027

@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 Feb 26, 2024
@Jipegien
Copy link
Member

@Jipegien Jipegien 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 Feb 27, 2024
@Jipegien Jipegien added this to the Release 6.0.0 milestone Feb 27, 2024
@SouadHadjiat SouadHadjiat self-assigned this Feb 27, 2024
@SouadHadjiat
Copy link
Member

Fixed by OpenCTI-Platform/connectors#1865

@SouadHadjiat SouadHadjiat added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 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

No branches or pull requests

3 participants