-
Notifications
You must be signed in to change notification settings - Fork 611
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
[Bug] Marking an alert as read do not update it's "updatedAt" nor "updatedBy" field #2292
Comments
dupliates #2262 |
Hi @To-om, Thanks for your reply. Though, I'm sorry I don't understand why this issue was closed as duplicate. It is not the exact same issue. The "updatedAt" and"updatedBy" fields always have a "null" value even when the alert has been maked as read. This issue is visible when searching an alert with the /api/alert/_search API call. (With the search panel from TheHive Web UI or with the TheHive4py.api find_alerts() function for instance). Edit to make the issue clearer : |
weird, I've just checked and I can't reproduce this behaviour. |
Thank you @Dilaw9 for this issue. It is now fixed. |
Request Type
Bug
Work Environment
TheHive 4.1.15
Problem Description
Marking as read an alert do not update its "updatedAt" nor "updatedBy" field when searching the alert with the /api/alert/_search API call.
Steps to Reproduce
1 - create an alert.
2 - mark it as read.
3 - search this same alert through the search panel of TheHive UI
Complementary information
This bug also impacts TheHive4py.api find_alerts() method as it also relies on the /api/alert/_search API call.
The text was updated successfully, but these errors were encountered: