action #45278

Improve developer mode for re-needling use case

Added by mkittler over 1 year ago. Updated about 1 year ago.

Status:ResolvedStart date:18/12/2018
Priority:NormalDue date:
Assignee:mkittler% Done:

0%

Category:-
Target version:Current Sprint
Difficulty:
Duration:

Description

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_updated flag 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.


Related issues

Related to openQA Project - action #44969: Wrong 'new needle with matching tags has been created sin... Resolved 10/12/2018

History

#1 Updated by mkittler over 1 year ago

  • Description updated (diff)
  • Status changed from New to In Progress

#2 Updated by mkittler over 1 year ago

  • Description updated (diff)

#3 Updated by mkittler over 1 year ago

  • Related to action #44969: Wrong 'new needle with matching tags has been created since the job started' warning message added

#6 Updated by mkittler about 1 year ago

  • Description updated (diff)

#8 Updated by mkittler about 1 year ago

  • Status changed from In Progress to Resolved

The PRs have been merged.

The 2 remaining points wouldn't be that easy to implement. It also wouldn't gain us much (from my point of view) so likely not worth the effort.

Also available in: Atom PDF