Description of problem: Hi, problem is that beaker allow us to add email adresses to cc $ bkr workflow-simple --help |grep cc --cc=CC Specify additional email addresses to notify what is very useful, when you schedule some job for another user. It is possible to see these jobs where I'm cc'ed at page: https://beaker.engineering.redhat.com/jobs/mine I think that it is senseful, and propably very useful feature to see the CCed jobs. Now propably it works, that it sends email, after job end, but it is unable to see job state (for example if it end in short time until you know job ID) So my question is, it is possible to add cced job ids into mine jobs? or to do it somehow searchable to be able see these jobs (second option is to be able search via CC option for example add option cc for search query https://beaker.engineering.redhat.com/jobs/?jobsearch-0.table=Cc&jobsearch-0.operation=contains&jobsearch-0.value=jscotka&Search=Search Thanks&Regards Honza
Having all the jobs I'm CCed to on my "My Jobs" list would be very nice feature. use-case: automation scripts that schedules various jobs on behalf of other people, currently owners of these jobs are not aware of them because they don't appear on their "My jobs" pages.
Hello, any updated on this one?
There should be also feature, that when I'm CCed, it means I able to work with job (cancel, ACK/NACK recipes) I can fill another bug for the second request (but implementation seems to be very close, same as previous request) Thanks Honza The bug is need to deal with automated job scheduling for various people.
I am loathe to use the the CC list for anything other than emailing people, certainly not as a conduit for permissions.
As for showing jobs you are CC'ed on within a single page, this seems like a good idea. Perhaps on the 'My Jobs' page, but with a toggle that can hide/show the CC'ed jobs.
I would note that the job cc list contains only e-mail addresses, not Beaker users, specifically so that non-user e-mail addresses can be cc'ed (mailing lists etc). Maybe a better way to address people's needs here would be some combination of: * proxy authentication, so that a service can submit jobs on behalf of users (and the user becomes the actual owner of the job) * some way to list the jobs submitted by a specific user, e.g. /jobs/<username> (bug 694061)
But I thing that solution with CC means also permission (no matter that there are mailing lists or another users, because havent login abilities to beaker) seems to me easy to implement and also give you nice features. Another option is to add new field of users/ groups what are allowed to deal with job. It is nice and universal solution, but need propably bigger changes in beaker. (vice versa CC-list as permisson list is straightforward and propably it is only one added line which check if I'm able to deal with job. At least mentioned filtering or show CCed jobs in mine (hideable) is also enought Thanks Honza
I suppose we could attempt to look up the user via the email address, If we can look them up then add them to a user_cc list otherwise add them to email_cc list. But we would not bring in ACL's until the group re-work has been done.
We will not be implementing this concept in this form. Instead, Beaker 1.0 will allow jobs to be submitted explicitly on behalf of a group, in which case all members of that group will see those jobs appear in their "My Jobs" list (see BZ#908185). Filtering options will be available to exclude group jobs from the list when so desired.
Please see my use-case in comment#1 - to make it work using the group model I'd have to create 40 groups for 40 people (each including 1 QE person and the automation user). I'd also have to create and maintain a service that would create/delete groups based on orgchart changes. That's plain ugly, please don't make me do it :)
The combination of group jobs (with all members of a group seeing shared jobs in their My Group Jobs page) and submission delegates (with users seeing jobs submitted on their behalf in their My Jobs page) should cover the different use cases discussed in this RFE. Any requests for further refinements to those features can be filed as new BZ entries :)