Red Hat Bugzilla – Bug 829825
[RFE] Improve the Highlight Used in My Subscriptions Tab
Last modified: 2013-01-07 22:54:43 EST
Description of problem:
One of the comments we got from the focus group was that the yellow highlight we show in the My Subscriptions tab when a subscription is expiring soon was unclear (we give no context for why it's highlighted). When that subscription is selected, the user can no longer see the highlight, as it gets replaced by the selection highlight.
I propose we remove our current highlight from the subscription in the table and instead apply that highlight to the date field in the details pane, and use a status icon in the table. We would also have a tooltip for the icons to explain the different cases.
We already leave room for icons in the My Subscriptions table. Would we be able to selectively display icons in that spot if the subscription is expiring soon, has expired, or is future subscribed and leave it blank if everything is normal? We could do a tooltip for the icons if they were moused over and show a brief message, saying "Subscription Expiring Soon", "Subscription Expired", "Subscription Future Subscribed". Icons would show through the selection highlight, and allow for a tooltip to show context if they don't know what it's there for, and we could also apply a highlight to the date field, to further call it out and add context, pointing them in the right direction to realize whats going on if they don't read the tooltip.
Use our yellow icon and a yellow highlight on the date row for subscriptions expiring soon or future subscribed.
Use our red icon and a red highlight on the date row for expired subscriptions.
Refs: master, subscription-manager-1.0.10-1-33-g0c25697
Merge: 69b03ed 0f07ab6
Author: Adrian Likins <email@example.com>
AuthorDate: Tue Jul 24 12:05:14 2012 -0400
Commit: Adrian Likins <firstname.lastname@example.org>
CommitDate: Tue Jul 24 12:05:14 2012 -0400
Available in subscription-manager-1.0.11+
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
The tool tips are not working as of version:
Throwing back for inclusion.
Tool tips are not native to GTK TreeViews. I found an add-on solution, but mreid and I determined that it was not polished enough to serve our needs. Instead we elected to leave the tool tips out altogether.
(In reply to comment #4)
> The tool tips are not working as of version:
> Throwing back for inclusion.
There were issues getting tooltips implemented like we wanted, and the way we could actually make them work was kind of hacky, and was dropped.
Since we couldn't get tooltips, Future Subscribed subscriptions shouldn't get a warning icon like we added for expiring subscriptions.
Sorry, I should have updated the BZ.
Created attachment 615410 [details]
Unsubscribe button is not disabled
Moving back to new as unsubscribe button is not disabled when nothing is selected
[root@localhost entitlement]# subscription-manager version
registered to: Unknown
server type: RHN Classic
Author: Alex Wood <email@example.com>
Date: Fri Sep 21 13:24:21 2012 -0400
829825: Disable unsubscribe button when nothing is selected.
Created attachment 630353 [details]
missing yellow icon and highlight on future subscription
(In reply to comment #0)
> Use our yellow icon and a yellow highlight on the date row for subscriptions
> expiring soon or future subscribed.
Moving back to ASSIGNED
attachment 630353 [details] was taken against subscription-manager-gui-1.0.23-1.el5
See comment #6:
"Since we couldn't get tooltips, Future Subscribed subscriptions shouldn't get a warning icon like we added for expiring subscriptions."
This is because highlighting future subscriptions the same way we highlight soon to expire subscriptions would make the highlighting ambiguous to the user. The tooltip was meant to counteract this ambiguity but couldn't be implemented for technical reasons.
Very well... Moving to VERIFIED minus the two exclusions in comment 6.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.