Bug 1873481 - Workspaces [Design Change]: "Items" are optional and thus can have zero items
Summary: Workspaces [Design Change]: "Items" are optional and thus can have zero items
Keywords:
Status: ON_QA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.6.0
Assignee: divgupta
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-28 13:21 UTC by divgupta
Modified: 2020-09-09 07:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Github openshift console pull 6472 None open Bug 1873481: Show workspace volume-type item fields only when added 2020-08-28 13:22:14 UTC

Description divgupta 2020-08-28 13:21:54 UTC
Description of problem:
Design issue (imo). When using the Start Pipeline modal, the workspaces section has a 3 step process for each workspace:

1.Select the type of workspace
2.Select the resource from that type
3.Add "items" of data to the workspace data for the Pipeline Run

The design issue is two pronged:

1.Why are the "key" and "path" items stacked? It's a reasonably wide modal that we likely could / should show on the same row
2.Why is the "items" section forced to have one row that is optional and in the follow use-case not even needed... it takes up space in an already noisy modal

How reproducible: Always

Steps to Reproduce:
1.Create a pipeline with workspace(s)
2.Open the Start Pipeline modal
3.Select the Secret/ConfigMap option
4.Select the required Secret/ConfigMap
  
Actual results:
Unnecessary item row is shown

Expected results:
Ideally see both options on the same line & show zero rows off the start (user can add them and remove them at their will)


Note You need to log in before you can comment on or make changes to this bug.