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

Export of Knowledge in Relationship view generates an error #3915

Closed
Archidoit opened this issue Aug 3, 2023 · 0 comments · Fixed by #3916
Closed

Export of Knowledge in Relationship view generates an error #3915

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

Description

Export of Knowledge in Relationship view generates an error

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

Go to a campaign. Go to the Knowledge tab. Select an entity type (ex: Tool).
Add an entity (a tool in the exemple).
Go to the relationship view.
Generate an export (in JSON for instance).
An error occurs.
image

@Archidoit Archidoit added the bug use for describing something not working as expected label Aug 3, 2023
@Archidoit Archidoit self-assigned this Aug 3, 2023
@Archidoit Archidoit added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 3, 2023
@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 3, 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
Development

Successfully merging a pull request may close this issue.

2 participants