Bug 1015007 - No "comment" link on failed recipes
Summary: No "comment" link on failed recipes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.15.1
Assignee: Dan Callaghan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 09:52 UTC by Jiri Benc
Modified: 2018-02-06 00:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-23 06:58:01 UTC
Embargoed:


Attachments (Terms of Use)
Screenshot (27.44 KB, image/png)
2013-10-03 09:52 UTC, Jiri Benc
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1013445 0 unspecified CLOSED [RFE] Improve display of recipe details in job results 2021-02-22 00:41:40 UTC

Internal Links: 1013445

Description Jiri Benc 2013-10-03 09:52:21 UTC
Created attachment 806996 [details]
Screenshot

After the recent redesign, the "comment" link next to Ack/Nak/Needs Review radio buttons is missing on failed recipes. It's present on recipes that succeeded but it's missing on recipes that failed (where it's more needed). Clicking Ack or Nak doesn't change that.

Comment 2 Dan Callaghan 2013-10-09 11:26:15 UTC
Patch to fix the display issues with the current ack panel:

http://gerrit.beaker-project.org/2341

Proposed patch to update the UI to something a bit nicer:

http://gerrit.beaker-project.org/2342

The latter patch might be better as part of a wider overhaul of the job page so might not be suitable for 0.15.1.

Comment 3 Nick Coghlan 2013-10-10 03:10:40 UTC
Agreed that the second patch would be better considered as part of something like bug 1013445 in Beaker 0.16 rather than being included in 0.15.1.

First patch looks good, though.

Comment 7 Raymond Mancy 2013-10-23 06:58:01 UTC
beaker 0.15.1 has been released.


Note You need to log in before you can comment on or make changes to this bug.