Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-69136

Make the user aware that the new VNC connection might drop an existing one

XMLWordPrintable

    • polite-vnc Clone
    • Product / Portfolio Work
    • 77
    • False
    • Hide

      None

      Show
      None
    • False
      • Opening the console tab in the UI does not kill an existing VNC connection if the user does not request it explicitly
    • None
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, po-ready, qe-ready, ux-ready
    • Yes

      Goal

      If a user creates a new VNC connection, even without intention by opening the console tab in the UI, would drop an already existing VNC connection.

      User Stories

      • As a UI user, I would like to open the console tab, without unintentionally killing already existing VNC session.
      •  

      Non-Requirements

      Notes

      • Any additional details or decisions made/needed

          1.
          		 upstream roadmap issue Sub-task Closed Undefined Unassigned
          2.
          		 upstream design Sub-task New Undefined Unassigned
          3.
          		 upstream documentation Sub-task New Undefined Unassigned
          4.
          		 upgrade consideration Sub-task New Undefined Unassigned
          5.
          		 test plans in polarion Sub-task New Undefined Unassigned
          6.
          		 automated tests Sub-task New Undefined Unassigned
          7.
          		 downstream documentation merged Sub-task Closed Undefined Unassigned
          8.
          		 CNV QE DevOps Requirement/Enablement Sub-task New Undefined Unassigned

              victortoso@redhat.com Victor Toso
              dholler@redhat.com Dominik Holler
              Geetika Kapoor Geetika Kapoor
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: