Options when clicking stop button

[prasm313]

Describe the new feature you would like to see
As discussed in previous UX-meetings the ongoing mission card will look like this:

There are four actions we may want to do with active missions:

1. Cancel mission and skip to next mission, keep queue
2. Pause mission, with the possibility to resume, keep queue
3. Cancel mission and stop robot in current location, delete queue
4. Cancel mission and return to home, delete queue

The first point will be solved by the "Next" button. The last three should be addressed in a pop-up when clicking the "Pause" button.

Describe the solution you'd like
Pop-up with text and buttons similar to:

If the user chooses to cancel:

How will this feature affect the current Threat Model?
N/A

[prasm313]

I will have a chat with UX designer

[anetteu]

Some thoughts about this:

Considering safety, I think the following behavior shall be considered:

1. When the stop button is pressed, the robot stops immediately
2. The robot shall not move before an action for the robot to do so is taken

Furthermore, I suggest that:

1. There is only one stop button. That stop button should stop the robot(s), and be independent of missions.
2. This stop button should be on a fixed position on the screen on all pages. It should not be necessary to navigate to access the stop button. Consider to place pause and stop button in fixed position  #901 (closed but not implemented?)
3. The robot shall stop immediately after pressing the button, without the need to answer any pop-up etc.
4. Pause button can be removed.
5. After the stop button is pressed, and the robot has stop any movement, the user can be given some options, for example:

• Continue
• Cancel current mission and continue with queued missions if any
• Cancel all missions and go home
• Cancel all missions and remain at the same position
• etc.

Which should comply with the scenarios described above

This will address what I see as challenges with the solution we have today:

1. The stop and pause buttons are not available on all pages and not in a fixed position. Navigation and scrolling is necessary to access the stop button. This can delay the operator in stopping the robot.
2. The robot does not stop until the operator has answered the pop-up. This delays the stop off the robot. Furthermore, if it is important to stop the robot fast, the operator will most likely just click and not actually read the pop-up.
3. The stop button does only stop the mission and not the robot. If there are missions in the queue, the robot will start driving again soon after the stop button is pressed even if there are no actions taken by operator.

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.