Epic Goal*

Changes in web-console/GUI and OC CLI where we will change number of update recommendations users see.

• We want to limit the number of update recommendations users see by-default. Because in our opinion a long list the older versions does not help. 
  • We want to provide command line line option for users to see the older versions only when they are interested.
• Move conditional risks/known risks out of the switch/button in the GUI. By-default users should see recommended updates as well as update options with known issues/conditional risks
  • Conditional risks should have some way to identify them as risks/known issues (example : adding asterisks beginning or end of the risk)
• We will adjust the ordering of recommended updates based on freshness

Why

• Customers still think that RH removes edges because they are not aware of the flag that hides update options with known issues/ conditional risks.
• Even when they notice the output advertising --include-not-recommended, customers might assume anything "not recommended" is too complicated to be worth reading about, when sometimes the assessed risk has a straightforward mitigation, and is closer to being a release note. We want to make those messages more accessible, without requiring customers to opt in.
• A long list of update recommendations does not help users/customers. We want to reduce the paradox of choices.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing - Tests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Other