Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2062410

Summary: When filtering by type, for example "Physical RHEL" or "Public Cloud", filter the underneath table as well
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: Waldirio M Pinheiro <wpinheir>
Component: Subscription WatchAssignee: Kevin Howell <khowell>
Status: CLOSED NOTABUG QA Contact: Jon Allen <jallen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: dozdowsk, jkreft, nkathole, rjerrido, sghai, sjagtap
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 13:55:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2022-03-09 17:50:44 UTC 
Description of problem:
Currently, when clicking over the links "Physical RHEL" or "Public Cloud" we can see that only the graph get updated. However, it's important to the customer be able to see only the servers that are part of that selection as well.

For example, if the customer would like to see in the table servers from cloud, there is no way to filter at this moment. Applying the filter all together will be really useful.

In a future, we will split also "Virtualized RHEL" maybe in two, creating a new one for Hypervisors, in this case, once the customer filter by Hypervisors, they will be able to see ONLY the hypervisor also with the # of guests on top of each one, as well sockets, which will help them in the next step.

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


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
The table still presenting the whole information

Expected results:
Once the customer click over any option to filter in the graph, the table will get updated as well.

Additional info:
Comment 4 Justin Kreft 2022-04-07 15:41:49 UTC 
If we filter on SLA or usage, which is a first class filter we do get the inventory table. The graph filters are intended to help with problems of axis scale. 

They're not intended to be first class filters if they want. 

We need more information for why the intended behavior is not sufficient to the reported bug. 

First class filters will always define the data that is represented in the graph. Clicking on the graph is seperate funtionality.
Comment 5 Justin Kreft 2022-04-07 15:44:04 UTC 
Please close
Comment 7 Waldirio M Pinheiro 2022-04-19 17:30:58 UTC 
Hello,

Thank you for the heads up. that said, I believe the request here should be to the first class filter then, add a new filter, for example

Source:
  - Physical RHEL
  - Virtualized RHEL
  - Public cloud

and when selecting only one, the table at the bottom should be presenting only the information based on the filter.


Thank you
Waldirio
Comment 8 Justin Kreft 2022-04-19 20:04:51 UTC 
This isn't a bug. It is a UX request.
Closing.
Comment 9 Rich Jerrido 2022-04-19 20:31:38 UTC 
(In reply to Waldirio M Pinheiro from comment #7)
> Hello,
> 
> Thank you for the heads up. that said, I believe the request here should be
> to the first class filter then, add a new filter, for example
> 
> Source:
>   - Physical RHEL
>   - Virtualized RHEL
>   - Public cloud
> 
> and when selecting only one, the table at the bottom should be presenting
> only the information based on the filter.
> 
> 
> Thank you
> Waldirio

By adding these filters, what customer workflows do we enable?

Swatch is not a generic inventory browser, nor are there subscriptions which are sold based on being solely physical, virtual, or cloud. So even if we could filter the inventory based on its system fact, we cannot filter the subscriptions. This would lead to even more customer confusion. 


If you believe there is value in filtering the inventory based on infrastructure type, please reassign this RFE to the inventory component. Alternatively, reassign this RFE to the export component/feature.
Comment 10 Waldirio M Pinheiro 2022-04-20 16:56:54 UTC 
Hello,

In general, when presenting swatch to our customers, they would like to export or filter the servers by type. Currently, they can export using the API/crhc-cli, but via webUI, they need to click on "Type" header, and then the information will be reordered. This is the way that they are seeing/filtering the information.

One valid example is, if they would like to see only physical/hypervisors servers, currently, they reorder and some times they have to move 3, 4, 5 pages to start seeing what they are looking for.

I didn't add any customer cases here, but I can do it later, no problem at all. This is a common point in all the swatch cases that I am/was working on.


Just one question about your statement

> If you believe there is value in filtering the inventory based on infrastructure type, please reassign this RFE to the inventory component. Alternatively, reassign this RFE to the export component/feature.

Humm, I'm not sure, there are rules on swatch, even if we create the filter for type on hbi, the information will be different and the customer is looking for it on swatch.



Please, let me know if you have additional questions or concerns.

Thank you
Waldirio