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

Error on instance context #6549

Closed
frapuks opened this issue Apr 3, 2024 · 0 comments · Fixed by #6553
Closed

Error on instance context #6549

frapuks opened this issue Apr 3, 2024 · 0 comments · Fixed by #6553
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)
Milestone

Comments

@frapuks
Copy link
Member

frapuks commented Apr 3, 2024

Description

  • Error on page after click on view the element from Settings / Activity / Events / select one

Environment

  1. OS (where OpenCTI server runs): Windows 11
  2. OpenCTI version: 6.0.8
  3. OpenCTI client: frontend / graphql

Reproducible Steps

  • Go to Settings / Activity / Events
  • Filter with Event Type = mutation
  • Select one (=> open right panel)
  • Click on view the element => navigate to an url .../dashboard/id/:id
  • Error

Expected Output

  • Not sure !!! Display detail of object or relation ship

Actual Output

  • Page Error, because graphQL query is broken

Additional information

  • Graph QL error : Runtime Object type "Settings" is not a possible type for "StixObjectOrStixRelationship".
  • In right pannel, when you select a delete mutation, the button view the element create a page not found error. May be it's normal, but in this case, don't display the button.

Screenshots

bug

@frapuks frapuks added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 3, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.9, Release 6.0.10 Apr 3, 2024
@Archidoit Archidoit self-assigned this Apr 3, 2024
@Archidoit Archidoit removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 3, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.10, Release 6.0.9 Apr 3, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 3, 2024
Archidoit added a commit that referenced this issue Apr 3, 2024
Archidoit added a commit that referenced this issue Apr 4, 2024
Archidoit added a commit that referenced this issue Apr 5, 2024
Archidoit added a commit that referenced this issue Apr 8, 2024
Archidoit added a commit that referenced this issue Apr 15, 2024
Archidoit added a commit that referenced this issue May 7, 2024
Archidoit added a commit that referenced this issue May 15, 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)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants