Bug 584725
Summary: | Default results choise in personal preferences | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Zbysek MRAZ <zmraz> |
Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 0.5 | CC: | azelinka, bpeck, dcallagh, dkovalsk, ebaak, ebenes, 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: | 2011-01-27 16:50:04 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
Zbysek MRAZ
2010-04-22 09:44:04 UTC
One more problem with the default choice: https://beaker-stage.app.eng.bos.redhat.com/recipes/953#task4829 This is link to a task results number 4829 but when you open it tasks 4830 and 4831 are displayed. I guess the cause is that 4829 has PASSed thus gets filtered out and 4830 is the first failing task in the job after 4928... Quite confusing. I've changed the default display to be compressed and it gives you the choice to display all results or only failed results (if there are failed results). I think I still need to deal with the linking which is mentioned in comment 1. The changes are live on beaker-stage, can you please check if this is a step in the right direction? Thanks Yes, that's maybe even better, when you are looking for particular acrhitecture for example. Thank you. A few things have changed since this report has been filed. Is there actually anything else requested or can we close this out? I'm pretty much happy with current state. This can be closed from my point of view. Great :) Ales (and everyone else), any objections to closing this bug? Nope, +1 to closing this bug. |