Context
Sometimes the matching algorithm groups a sequence into the wrong alert. Users (agent/admin) should be able to fix this from the platform.
Technical aspects
pyro-api now exposes POST /alerts/{alert_id}/sequences/{sequence_id}/unmatch (pyronear/pyro-api#582), which detaches a sequence from an alert and recomputes the alert state. If the sequence becomes orphaned, a new alert is created for it. The endpoint rejects the call when the alert has a single sequence.
Proposed UX:
- In the alert detail view, add an "unmatch" button next to the currently selected sequence (e.g. in
SequenceSelector or AlertActionButtons)
- Show a confirmation dialog before unmatching
- Hide or disable the button when the alert has only one sequence
- On success, refresh the alert data (the sequence may now belong to a new alert)
Context
Sometimes the matching algorithm groups a sequence into the wrong alert. Users (agent/admin) should be able to fix this from the platform.
Technical aspects
pyro-api now exposes
POST /alerts/{alert_id}/sequences/{sequence_id}/unmatch(pyronear/pyro-api#582), which detaches a sequence from an alert and recomputes the alert state. If the sequence becomes orphaned, a new alert is created for it. The endpoint rejects the call when the alert has a single sequence.Proposed UX:
SequenceSelectororAlertActionButtons)