Hide Forgot
Description of problem: While trying to go back and debug failures. I was trying to correlate test failures with outage notifications. It is proving difficult. Looking at job/recipes. Each saying different Start times. Started 10 days ago and finished in 07:43:29. Started 19 days ago and finished in 01:22:19. Started 11 days ago and finished in 10:10:11. Started 10 days ago and finished in 00:43:29. Is there a specific reason why a date is not used? Meaning rather then above: Started 082216 and finished in 07:43:29. Started 081316 and finished in 01:22:19. Started 082116 and finished in 10:10:11. Started 082216 and finished in 00:43:29. Or Started Aug 22 2016 and finished in 07:43:29. Started Aug 13 2016 and finished in 01:22:19. Started Aug 21 2016 and finished in 10:10:11. Started Aug 22 2016 and finished in 00:43:29. It makes it much easier to track issue. Verses have to Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
<The Bug was submitted before I finished my thought.> It makes it much easier to track issue. Verses have to manually due the date change. Thanks, Jeff
All of the "human friendly" timestamps ("10 days ago", etc) you can hover your mouse over them and a tooltip will show the exact timestamp.
Hi Dan, Thanks for the tip. Was the "human friendly" change something some one asked for? or was it something that came back organically with the major UI update? It is still a PITA to have to go hover over everything. In order to correlate times. Thanks, Jeff
Hello, thank you for opening issue in Beaker project. This issue was marked with component "web ui". As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX. New UI will be reimplemented within new versions of Beaker. If you have any questions feel free to reach out to me. Best regards, Martin <martin.styk>