UX: Stopping multiple pipeline jobs is unnecessarily painful
Summary
Stopping multiple jobs from the Jobs list takes at least two clicks and ten seconds per Job.
Steps to reproduce
Navigate to the the CI Jobs list page. Use the X
button to cancel a running job.
What is the current bug behavior?
One is brought to the job log.
What is the expected correct behavior?
The behavior should be similar to that of Pipeline cancellation: a modal dialogue asking for confirmation is presented and after cancelling the Job list should be refreshed.
There is no reason to bring the user to the log of a cancelled job.
Possible fixes
Emulate the behavior of Pipeline cancellation in the Job cancellation interface.