Bug 584897
Summary: | [RFE] compact results view | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Ales Zelinka <azelinka> |
Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 0.5 | CC: | bpeck, ebaak, kbaker, mcsontos, rmancy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-03 07:00:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ales Zelinka
2010-04-22 16:49:43 UTC
I've made some changes on beaker-stage that incorporate some of the things you mention. Can you look and see if that is a step in the right direction? Just so you know, People complained about the levels that they had to open in the old rhts. Hopefully I can strike some middle ground where everyone is somewhat happy. I think it will be hard to make everyone happy. How about letting users set preferences so their default view unrolls as they like? I agree. (In reply to comment #1) > I've made some changes on beaker-stage that incorporate some of the things you > mention. Can you look and see if that is a step in the right direction? It is, thanks. The new collapsed recipe view corresponds to view#1 from comment#0 > > Just so you know, People complained about the levels that they had to open in > the old rhts. I see. Than there probably isn't one result page layout to satisfy all users and I'd go with the configurable level of details Kevin mentions: * levels of details as described in comment#0 * default level configurable via preferences * controls on result page - the ones currently present (per-recipe) and a global one - expanding/collapsing all recipes at once * level of details embedded in URL so that links can be sent for a particular detail level What do you think? I haven't had any complaints since the new layout change. and Today's update loads the task results as an ajax call, this should resolve the performance issues. Can I close this? The non/all detail level are satisfied by collapsing/expanding individual recipes of a job. And for the intermediate level of details (view#2), matrix report (that is, by the way, absolutely awesome) can be used. Only two minor [RFE] remains: - global "[hide|show] [all|failed] results" buttons that will work on all the recipes at once - link the matrix report from job result page (even though one job matrix report probably isn't the major use-case for it, it still is very useful) Should I file those as separate RFEs? Thanks Ales, Sorry for the very delayed response. If you could file these as seperate RFE's that would be great. |