Bug 1728747

Summary: task dashboard -- highilighting issues
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Tasks PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: aruzicka, inecas, magaphon
Target Milestone: 6.6.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: tfm-rubygem-foreman-tasks-0.15.9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:51:59 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:
Bug Depends On:    
Bug Blocks: 1718889    
Description Flags
image2 none

Description Peter Ondrejka 2019-07-10 15:17:14 UTC
Description of problem:

1. The highlihging of currently active elements is a bit inconsistent (see image1). I'd imagine that the inactive cards would be grayed-out as a whole, currently the titles and some text elements are never grayed out, which works against the quick realizing of which filters are actually applied.

2.Also when applying the old-style search filter (even an empty one), the donut charts from dashboard dissapear (see image2)

3. The table in Stopped card is a bit unclear about what is clickable. I tried the rownames without effect, therefore I assumed for a while the table is just informative -- would be nice to be consistent with the table style where clickable elements are blue.

4. Just a minor annoyance, I'd increase the spacing between the number and "Total" within donuts.

Comment 3 Peter Ondrejka 2019-07-10 15:22:25 UTC
Created attachment 1589131 [details]

Comment 4 Peter Ondrejka 2019-07-10 15:23:12 UTC
Created attachment 1589133 [details]

Comment 10 Peter Ondrejka 2019-09-16 11:22:45 UTC
Verified on Sat 6.6 snap 20, issues 1. and 3. were fixed

Comment 11 Bryan Kearney 2019-10-22 19:51:59 UTC
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.