You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
similarity GET parameter of /api/alert/<ID> route is broken.
According to documentation, /api/alert/:alertId provides a parameter named similarity which can be set to 1 to fill the similarCases field of the output (ie. /api/alert/~20672?similarity=1). However, the server answer with a 404 error: {"type":"NotFoundError","message":"Alert not found"}. Note that the alert exist and the error disapear when similarity is set to 0 or not set.
Steps to Reproduce
Create 2 alerts with same artifacts
Transform one of the alert to a Case
Query the API with the id of the other alert: /api/alert/<ID>?similarity=1
Possible Solutions
Fix with the expected behavior
The text was updated successfully, but these errors were encountered:
Zeecka
changed the title
[Bug] "similarity" parameter of GET /alert/<ID> doesnt work
[Bug] "similarity" parameter of GET /api/alert/<ID> doesnt work
Apr 28, 2021
Request Type
Bug
Work Environment
Problem Description
similarity
GET parameter of/api/alert/<ID>
route is broken.According to documentation,
/api/alert/:alertId
provides a parameter namedsimilarity
which can be set to1
to fill thesimilarCases
field of the output (ie./api/alert/~20672?similarity=1
). However, the server answer with a 404 error:{"type":"NotFoundError","message":"Alert not found"}
. Note that the alert exist and the error disapear when similarity is set to 0 or not set.Steps to Reproduce
/api/alert/<ID>?similarity=1
Possible Solutions
Fix with the expected behavior
The text was updated successfully, but these errors were encountered: