action #37375

action #14818: [EPIC] Interactive mode is an usability disaster

action #36442: Access to running SUTs for System Developers

Create UI elements for developer sessions and update them via WS connection

Added by mkittler almost 2 years ago. Updated almost 2 years ago.

Status:ResolvedStart date:14/06/2018
Priority:NormalDue date:
Assignee:mkittler% Done:

0%

Category:-
Target version:Done
Difficulty:
Duration:

Description

We need to display the status information somewhere and of add the controls for the developer mode.

I would propose something similar to the already existing filter forms. Expanding this panel means opening the developer session. Other users can still see the status in the panel header. Eg.:

  • screenshot_20180614_113001
  • screenshot_20180614_113134

History

#2 Updated by mkittler almost 2 years ago

WIP-PR: https://github.com/os-autoinst/openQA/pull/1691

However, I'll continue to work on branch of @foursixnine which is based on this PR but already contains the status-only ws route in VNC instruction.


Further things mentioned in the planning today:

  • Move the live tab into the details.
  • Ask user what he wants first, then open the developer session. You don't start the session as such - you become the developer and happen to have a tab open.
  • Don't make the trigger for the developer session too visible so it isn't accidental enabled by random users. ?
  • Remove links to developer console, PR: https://github.com/os-autoinst/openQA/pull/1692 DONE

#3 Updated by mkittler almost 2 years ago

See parent ticket for updates on this.

#4 Updated by mkittler almost 2 years ago

  • Status changed from In Progress to Feedback

#5 Updated by mkittler almost 2 years ago

  • Status changed from Feedback to In Progress

#6 Updated by mkittler almost 2 years ago

  • Status changed from In Progress to Resolved

#7 Updated by szarate almost 2 years ago

  • Target version changed from Current Sprint to Done

Also available in: Atom PDF