-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
polite-vnc
-
Product / Portfolio Work
-
77
-
False
-
-
False
-
- Opening the console tab in the UI does not kill an existing VNC connection if the user does not request it explicitly
-
None
-
In Progress
-
20% To Do, 20% In Progress, 60% Done
-
dev-ready, doc-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.
UX doc
https://docs.google.com/document/d/1MJFOrB512smthxIDl5QeZWT4D0cN0FnhPoFNz19fHkk/edit?usp=sharing
Non-Requirements
- This epic is about single session VNC, multi session VNC is covered by https://issues.redhat.com/browse/VIRTSTRAT-488
Notes
- Any additional details or decisions made/needed
- is cloned by
-
-
- New
-
-
-
- Closed
-
- relates to
-
CNV-60117 Regular VNC console disconnect, due to competing request between the VNC thumbnail, and a full screen VNC view.
-
- POST
-
- links to
1.
|
upstream roadmap issue |
|
New | 
|
Unassigned |
2.
|
upstream design |
|
New |
|
Unassigned |
3.
|
upstream documentation |
|
New |
|
Unassigned |
4.
|
upgrade consideration |
|
New |
|
Unassigned |
5.
|
test plans in polarion |
|
New |
|
Unassigned |
6.
|
automated tests |
|
New |
|
Unassigned |
7.
|
downstream documentation merged |
|
New |
|
Unassigned |
8.
|
CNV QE DevOps Requirement/Enablement |
|
New |
|
Unassigned |