Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1015114

Summary: Sorting columns in My subscription tab on Quantity is ambiguous
Product: Red Hat Enterprise Linux 7 Reporter: Sharath Dwaral <fsharath>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED NOTABUG QA Contact: John Sefler <jsefler>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: awood, ckozak, jgalipea, jmolet, jsefler, mreid, redakkan
Target Milestone: rc   
Target Release: 7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-22 15:22:37 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:
Bug Depends On:    
Bug Blocks: 863175    
Attachments:
Description Flags
Sorting in My Subscription tab on Quantity none

Description Sharath Dwaral 2013-10-03 13:15:50 UTC
Created attachment 807081 [details]
Sorting in My Subscription tab on Quantity

Description of problem:
Sorting columns in My subscription tab on Quantity is ambiguous. Not only do the subscriptions (parents) get sorted but also the stacked (children) quantities; which may be the expected behavior. 

If the Parent subscriptions are being sorted it is not clear on what criteria. This can be seen from the attachment.

Version-Release number of selected component (if applicable):
# subscription-manager version 
server type: Red Hat Subscription Management
subscription management server: 0.8.28-1
subscription-manager: 1.10.2-1.git.53.5d7d98f.el6
python-rhsm: 1.10.2-1.git.4.3048ab5.el6

How reproducible:
Always

Steps to Reproduce:
1. Edit facts so that subscriptions can be stacked
2. Stack different subscriptions from different group
3. Play with quantity header in My Subscription tab to sort them

Actual results:
See Attachment

Expected results:
It doesn't make sense to me why we are sorting on quantity in the first place when we have ignore it in "Contract Selection Window" and "All Available Subscriptions" tab. So I would prefer sorting on quantity be removed entirely.

If opted to retain this feature then it should be sorted in a better way as I find this to be confusing/ambiguous.

More Info:
https://bugzilla.redhat.com/show_bug.cgi?id=817938

Comment 2 Carter Kozak 2014-01-22 15:22:37 UTC
This appears to be working as intended.  it sorts by quantity on root rows first, which is empty string when there is a stack header.  The child rows are sorted properly in that case, so I don't think there's a problem, or a better way we could do this.  We do not ever want to break apart stacks.