[🐛 Bug]: Incident field can't be queried / filtered upon
While alerts might have linked incident :
You can't seem to be able to query them, using CEL, Facet, or filters in workflows :
They all are seen as None.
I found a similar issue that was previously reported and has been closed: [🐛 Bug]: incident field in alerts table. This issue was resolved by a pull request that fixed the UI to handle the incident field properly [1]. You might want to check if your version includes this fix or if there are any updates available that address this issue.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Update, after digging a bit more :
To match : "incident": "390701dd-0f3c-4c07-aff1-7b0b8208d2f8"
You need the CEL : incident.id == "390701dd0f3c4c07aff17b0b8208d2f8"
(Using SQLite)
@skynetigor can we take care of it in the backend? seems like some dialects keep UUIDs in different formats