Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 864039

Summary:	[RFE] show ack/nack status of all recipes, not just your own
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.9	CC:	aigao, asaha, azelinka, dcallagh, ebaak, rmancy, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	GroupModel
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-16 15:13:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	961580
Bug Blocks:

Description Ales Zelinka 2012-10-08 12:20:10 UTC

Description of problem:Currently I can't see if someone else's recipe is acked or nacked. 


Version-Release number of selected component (if applicable):
0.9.3 

Steps to Reproduce:
1. login as azelinka
2. open https://beaker.engineering.redhat.com/jobs/311092 
  
Actual results:
can't see which recipesets are acked and whcih are nacked

Expected results:
can see acks/nacks

Comment 1 Dan Callaghan 2013-02-07 03:16:36 UTC

This will be addressed by allowing users to submit jobs for groups, and allowing all group members to ack/nack group jobs.

Comment 2 Nick Coghlan 2013-05-10 04:06:08 UTC

It's possible this is superseded by bug 961580 - it should be revisited once that feature has been implemented.

Comment 3 Dan Callaghan 2014-05-22 00:10:20 UTC

Ales, have the group jobs and submission delegate features satisfied your needs here? Or do you still want to be able to see the ack/nack state of other people's jobs?

I think there's no reason to hide it (since in general, all details of all jobs are visible to all users). The only reason it's not visible already is probably because nobody bothered to implement a read-only view of ack/nack state in the UI.

Comment 4 Ales Zelinka 2014-06-16 15:13:10 UTC

Hmm, I no longer remember my usecase :) But I guess it had something to do with our automation that schedules user jobs under its own identity preventing users from seeing the ack/nack status. Submission delegates should fix that => closed-not

Comment 5 Ales Zelinka 2014-06-16 15:13:25 UTC

-a-bug