Updating alert's asignee resets the alerts filters
Categories
(Tree Management :: Perfherder, defect)
Tracking
(Not tracked)
People
(Reporter: alexandrui, Assigned: sclements)
Details
Attachments
(5 files)
Updating an alert's assignee from any framework/status resets the alert filters to talos/untriaged.
This is causing a tedious workflow for sheriffs that need to set the filters again after updating an alert status (except talos, offcourse).
The same thing happens when you're on a particular alert item instead of a particular filter.
Example: In raptor/untriaged try to assign un unassigned alert to yourself (press take or unassigned button and then press enter. The other way around (unassigning) happens the same thing.
| Reporter | ||
Comment 1•5 years ago
|
||
| Reporter | ||
Comment 2•5 years ago
|
||
| Reporter | ||
Comment 3•5 years ago
|
||
| Reporter | ||
Comment 4•5 years ago
|
||
| Assignee | ||
Comment 5•5 years ago
|
||
This is so interesting.... it appears that hitting enter on that input element is acting like a submit event, causing a full page reload which is why the filters are reset. No idea why this would be happening with the routing change, but calling event.preventDefault in the onKeyPress function solves the problem.
I'll submit a patch for it but if you happen to see this happening somewhere else, this should solve the issue :)
| Assignee | ||
Updated•5 years ago
|
Comment 6•5 years ago
|
||
| Assignee | ||
Comment 7•5 years ago
|
||
The patch has been merged and deployed to production.
| Reporter | ||
Comment 8•5 years ago
|
||
(In reply to Sarah Clements [:sclements] from comment #7)
The patch has been merged and deployed to production.
Thank you very much for your quick fix, Sarah!
Description
•