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
Describe the improvement you would like to see
Currently notification (the bell in the header) and banner features are duplicates of each other. Suggested new solution is that banner will handle information that is relevant for the user while using flotilla, like if a mission fails to get scheduled. Notifications should be use for things that occur when the user might not be actively using flotilla that is use full to know when checking at a later time.
Notification should:
Have timestamp and show newest first
Should have these kind of notifications:
Failed missions
Aborted mission. Eg. If safe zone gets activated during mission or robot health (like low battery) causing the mission to be aborted
Banner should:
Only be used for things that happened now because of something the user did or something that is actively happening
Should either: Not overwrite each other OR have such generic text that it doesn't matter that they overwrite each other
Example: If failing to schedule 2 missions only the last to fail will get banner as the first gets overwritten. Either have several or a generic enough message
Should have these kind of banners:
"Send to dock" being active and robots being released from dock
Failing to schedule a mission
Failure to fetch requested info (like echo missions or should this always be handled as a popup or something instead?)
Currently we have these alert types:
MissionFail -> Should be notification (should also partially successful give alert?)
RequestFail -> Should be banner
DockFail -> Is this a failed mission? Might be both banner and notification if the robot gets stuck in the field and require assistance
BlockedRobot -> Remove? Isar is no longer providing this information
RequestDock -> Should be banner (if aborting a mission because of this it will get covered by mission fail as well)
DismissDock -> Should be banner
DockSuccess -> Should be banner
TODO:
Remove existing notifications (not banners)
Implement notification for failed missions with timestamp, sorted by newest first
Remove banner for failed missions
How will this change existing functionality?
How will this improvement affect the current Threat Model?
The text was updated successfully, but these errors were encountered:
Describe the improvement you would like to see
Currently notification (the bell in the header) and banner features are duplicates of each other. Suggested new solution is that banner will handle information that is relevant for the user while using flotilla, like if a mission fails to get scheduled. Notifications should be use for things that occur when the user might not be actively using flotilla that is use full to know when checking at a later time.
Notification should:
Banner should:
Currently we have these alert types:
MissionFail -> Should be notification (should also partially successful give alert?)
RequestFail -> Should be banner
DockFail -> Is this a failed mission? Might be both banner and notification if the robot gets stuck in the field and require assistance
BlockedRobot -> Remove? Isar is no longer providing this information
RequestDock -> Should be banner (if aborting a mission because of this it will get covered by mission fail as well)
DismissDock -> Should be banner
DockSuccess -> Should be banner
TODO:
How will this change existing functionality?
How will this improvement affect the current Threat Model?
The text was updated successfully, but these errors were encountered: