Improve developer mode for re-needling use case
|Target version:||Current Sprint|
After a re-needling session with @okurz we noticed that there's room for improvement:
Remove the "job cancel" button. It can be clicked accidentally and people are wondering about the difference to the regular job cancel button (there is no difference). Ensure tool-tips are disappearing when hiding a button. Confirming the dialog for match level should work by pressing return. Triggering a restart from the needle editor should open the right job. The needle editor should not show wrong notifications about newly added needles. After a short investigation it seems there's nothing wrong with the code displaying those notifications. However, the
t_updatedflag of the entries in the needle database is updated unexpectedly.
Show the current command in the developer mode panel. Add button to stop as soon as possible. Wrap long lines in the live log. Ensure the live log does not get too long. Otherwise the browser tab freezes at a certain length.
- Resume directly from the needle editor.
- (Re)start a job to open the developer mode directly and pause it as soon as possible.
Maybe it makes sense to create tickets for some of them and maybe we already have some tickets.
Striked-out points are already implemented in the PRs mentioned in the comment.