Description of problem: Unable to 'Report a Problem' on systems I have admin privileges on. In previous version of Beaker I was always able to click 'Contact Owner' Then 'Report a problem' With version 0.19 of Beaker on systems I am not an Admin on I can still do 'Report a Problem'. On systems I am an admin on I only see 'Remove from Service' Where this becomes an issue, is on kernel-hw admin managed systems. Prviously when I would click 'Report a problem' it would send an email to the owner. In htis case kernel-hw. That email links into a ticket queue. A ticket wuld automatically be opened. Now when I click 'Remove from Service' no email is sent to the onwer and so no ticket is opened.
I tried to use the remove from service link but no email was sent.
This is becoming a major PITA. Every time I set a system to Broken i have to also open a RT for it.
Most recent attempt. https://beaker.engineering.redhat.com/view/hp-xw6400-02.lab.bos.redhat.com#scheduler-settings
In the UI design we didn't really account for the possibility that a user could have admin rights on a system, but still want to send an e-mail to its owner. We were working from the assumption that if you have admin rights then you can fix the system yourself, though of course that isn't necessarily always true. Those "quick action" buttons were only ever supposed to offer the most likely operations you would need to do, not every possible operation -- so I think it should continue to show "Remove from Service" in this case. (The fact that Remove from Service just opens the Scheduler Settings tab and doesn't actually do anything, is an unrelated flaw in the Condition stuff that we will fix up eventually.) The real issue here is that "Report a Problem" doesn't appear anywhere else on the page, so if it's not shown as a quick action button then you can't do it. I guess it should probably be in the Owner tab. The workaround (if you have a mail client that can handle mailto: links) is to click the owner's username and type your e-mail there.
(In reply to Dan Callaghan from comment #4) > In the UI design we didn't really account for the possibility that a user > could have admin rights on a system, but still want to send an e-mail to its > owner. We were working from the assumption that if you have admin rights > then you can fix the system yourself, though of course that isn't > necessarily always true. > > Those "quick action" buttons were only ever supposed to offer the most > likely operations you would need to do, not every possible operation -- so I > think it should continue to show "Remove from Service" in this case. (The > fact that Remove from Service just opens the Scheduler Settings tab and > doesn't actually do anything, is an unrelated flaw in the Condition stuff > that we will fix up eventually.) > > The real issue here is that "Report a Problem" doesn't appear anywhere else > on the page, so if it's not shown as a quick action button then you can't do > it. I guess it should probably be in the Owner tab. > > The workaround (if you have a mail client that can handle mailto: links) is > to click the owner's username and type your e-mail there. I guess we could put the "Report a Problem" button next to the "Rename" button to make it more explicitly as I cannot really think of a good place in the Owner tab.
Dear Jeff, since the bug is urgent, we could provide a quickfix by putting the button back for system owners like you. That goes against the ideas we have the UI - like Dan explained in comment 4 - but would provide what you were asking for. Having said that, the proper solution will take time (e.g. ~ 3 months) but will deliver a more consistent UI experience (fixing a few RFEs along the way like Bug 1039842 comment 9). It will also remove the quickfix - if implemented as a short term solution. My question is, is this acceptable or is this not an urgent Bug anymore so you'll be happy to wait for the proper solution?
Hi Roman, I am ok waiting for a solution that is consistent with the plan. No need to implement a short term fix. I found a button to report an issue with the system from the Job page. But, that means I have to find a job for a system I am trying to report an issue for. Thank you for checking, Jeff
Beaker 26.4 has been released.