Description of problem: When subscriptions are grouped together in the Satellite Web UI, this is misleading to the end user for a few reasons: 1. If you have 2 subscriptions grouped together (even if they are the same subscription) the values in the column (consumed, entitlements, start date, etc) all refer to the first entry. Meaning, users will have to drill down to see all consumed, when in reality, the summary should be what users see, not the first subscription. For intance, there is a case where 1 Ansible sub has 3700 entitlements, and the other has 50. The UI shows them grouped together, but only shows 3700 entitelments. This number should be summed and show 3750 in my opinion. 2. Users are allowed to choose 5, 10, 15, 20, 25 or 50 subscriptions at a time, per the drop down menu in the Web UI. However, when too many subscriptions are grouped together, 50+, it can change that number to 100, even though that is not a selection. Which seems like a UI bug. 3. Visually it is not intuitive. Perhaps a color, or something else to signifiy they are grouped. Also, when you do expand them down, I feel like the subs should be indented. Again, when you have too many subs grouped, 50+ (as a result of virt-who), it is not easy to look through. 4. There is also a chance of having uneven entries per page. For instance, the first page has 13 entries (1 through 100 subs), the second page has 1 entry (101-199 subs) and the third page as 6 entries (201-236 subs). I understand some of the entries are grouped, and weigh heavier, but it doesn't look good, or make sense to have uneven entries like that. I feel the entries should be counted as 1 (even if they are grouped). And don't count the subscriptions per page, just the entries. Version-Release number of selected component (if applicable): Satellite 6.5.3 How reproducible: 100% Steps to Reproduce: 1. Having several hypervisors with 50+ vm guests using a virtual subscription Actual results: This disrupts the whole UI layout, and the number per page option changes to 100, even though that is not an option originally. Expected results: UI should be able to handle this. And perhaps the logic, or layout should change to make this easier to understand. Additional info: