Bug 1866336 - [RHOCS Usability Study][Installation] Users were confused when the OCS installation installed others operators along with OCS operator
Summary: [RHOCS Usability Study][Installation] Users were confused when the OCS instal...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Shiri mordechay
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-05 11:37 UTC by Harish NV Rao
Modified: 2020-11-26 12:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-19 12:23:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Harish NV Rao 2020-08-05 11:37:45 UTC 
Description of problem:

After the installation, users found other operators along with OCS operator installed. As part of the OCS installation flow, users should be informed of the number of operators that will be installed. 

UX issue severity level: 4-Low (refer below mentioned doc for severity levels)

This BZ is being filed based on the Usability study conducted on RHOCS during July 2020. A complete report on this Usability study can be found here: https://docs.google.com/presentation/d/1w65Rl2ZsTew-TIqgKUaZ9Y-1DmG1Z4Y59sYQjYC_mMM/edit#slide=id.g547716335e_0_260


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Bipul Adhikari 2020-08-07 06:31:20 UTC 
Assigning it to UXD, to get some suggestion on how to make users aware of these extra operators.
Comment 2 Yuval 2020-08-10 08:03:08 UTC 
If I understood right from eran users should not see the other 2 operators installed. I'm not sure who is working on solving that @etamir
Comment 7 Yuval 2020-11-26 12:52:03 UTC 
already fixed, can be closed
Note You need to log in before you can comment on or make changes to this bug.