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

Dashboard exported on 6.0 can't be imported again (invalid version error) #6181

Closed
SouadHadjiat opened this issue Feb 29, 2024 · 0 comments · Fixed by #6184
Closed

Dashboard exported on 6.0 can't be imported again (invalid version error) #6181

SouadHadjiat opened this issue Feb 29, 2024 · 0 comments · Fixed by #6184
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

@SouadHadjiat
Copy link
Member

Description

When exporting a dashboard in json, then importing it again on the platform, we get this error :
Invalid version of the platform. Please upgrade your OpenCTI. Minimal version required: 5.12.16

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: 6.0.1
  3. OpenCTI client: frontend
  4. Other environment details: reproduced on prod and testing
@SouadHadjiat SouadHadjiat added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 29, 2024
@SouadHadjiat SouadHadjiat self-assigned this Feb 29, 2024
@SouadHadjiat SouadHadjiat removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 29, 2024
@SouadHadjiat SouadHadjiat linked a pull request Feb 29, 2024 that will close this issue
5 tasks
@SouadHadjiat SouadHadjiat added this to the Release 6.0.2 milestone Feb 29, 2024
@nino-filigran nino-filigran added the critical use to identify critical bug to fix ASAP label Feb 29, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 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 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.

3 participants