Description of problem: The current code for displaying the job details (/jobs/jobid) uses cookies (one per recipe) to maintain information regarding what results to display -- all,failed or none. While working on the solution to https://bugzilla.redhat.com/show_bug.cgi?id=674025, it was felt that a cookie-less solution may result in a better implementation to not only this bug, but the overall logic used in fetching the results for recipes. For example, if only a particular task's result is requested, it will only fetch the results of that recipe and not all the other recipes in the job. The alternative suggested by Dan was using the History API. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: See above. Additional info:
This is implemented for the new recipe page design. Expanded/collapsed tasks are reflected in the URL anchor, as in /recipes/123#task4,task5 with the usual fallback to localStorage in case the user re-opens the page with no anchor. http://gerrit.beaker-project.org/4755
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
The results-reporting-improvements-take3 branch has been merged to develop.
Beaker 23.0 has been released.