Bug 864039 - [RFE] show ack/nack status of all recipes, not just your own
Summary: [RFE] show ack/nack status of all recipes, not just your own
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.9
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard: GroupModel
Depends On: 961580
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-08 12:20 UTC by Ales Zelinka
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-16 15:13:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 908185 0 high CLOSED Allow to view all my jobs including group jobs 2021-02-22 00:41:40 UTC

Internal Links: 908185

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
Note You need to log in before you can comment on or make changes to this bug.