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.

Sign up for GitHub

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

Jump to bottom

Limit the history message length both in backend (when inserting) and frontend #2470

Closed
SamuelHassine opened this issue Oct 19, 2022 · 0 comments · Fixed by #2494
Closed

Limit the history message length both in backend (when inserting) and frontend #2470

SamuelHassine opened this issue Oct 19, 2022 · 0 comments · Fixed by #2494
Assignees
@Kedae
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
Release 5.4.0

Comments

@SamuelHassine
Copy link
Member

Use case

Limit the history message length both in backend (when inserting) and frontend.

See ChapsVision report in the Filigran instance.
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Oct 19, 2022
@SamuelHassine SamuelHassine added this to the Release 5.4.0 milestone Oct 19, 2022
@Kedae Kedae assigned Kedae and unassigned richard-julien Oct 24, 2022
@Kedae Kedae linked a pull request Oct 26, 2022 that will close this issue
[api/frontend] Truncate history message when they are too long (#2470) #2494
Merged
richard-julien added a commit that referenced this issue Nov 6, 2022
@richard-julien
[api] Adapt migration script (#2470)
7133038
richard-julien added a commit that referenced this issue Nov 6, 2022
@richard-julien
[api] Handle more elements in migration script / Simplify the limit s…
e84e01f 
…cript (#2470)
richard-julien added a commit that referenced this issue Nov 6, 2022
@Kedae @richard-julien
[api/frontend] Truncate history message when they are too long (#2470)
594bfed 
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 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Kedae Kedae

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
Milestone
Release 5.4.0
Development

Successfully merging a pull request may close this issue.

[api/frontend] Truncate history message when they are too long (#2470) OpenCTI-Platform/opencti
3 participants
@richard-julien @SamuelHassine @Kedae