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

STIX ID standard is useless to analysts but have the most visible spot in item pages #1781

Closed
8hur opened this issue Dec 21, 2021 · 0 comments · Fixed by #2489
Closed

STIX ID standard is useless to analysts but have the most visible spot in item pages #1781

8hur opened this issue Dec 21, 2021 · 0 comments · Fixed by #2489
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@8hur
Copy link

8hur commented Dec 21, 2021

Use case

STIX ID standard may be very important internally to OpenCTI but is useless to the ones adding of gathering information to the instance. This information however takes the most visible spot in any page after the title of the page.

Current Workaround

deal with it

Proposed Solution

move it to the bottom of the page or make it a toggle for developer mode

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Dec 21, 2021
@SamuelHassine SamuelHassine added this to the Release 5.4.0 milestone Dec 21, 2021
@SamuelHassine SamuelHassine self-assigned this Oct 2, 2022
richard-julien added a commit that referenced this issue Nov 9, 2022
Co-authored-by: Julien Richard <julien.richard@filigran.io>
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop 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