https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #95 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to David Cook from comment #92)
(In reply to Jonathan Druart from comment #89)
Created attachment 107405 [details] [review] [review] Bug 22417: Add the new permission manage_background_jobs
QA: Please answer the question in admin/background_jobs.pl
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
I can't 100% recall how background jobs are implemented in the web UI, but I find admin/background_jobs.pl to be a challenging topic.
In theory, any module (eg circ, acquisitions, etc) could use a background job, so shouldn't the UI be in the source module rather than in the admin module? (If that already is the case and I'm mistaken, then maybe just leave this script with "manage_background_jobs".)
What is the "source module"? I think that a user with manage_background_jobs should be able to access and manage (cancel, view, etc.) any jobs (done) However anyone who started a job should be allowed to manage this job (not done yet), but should we force a minimum permission or authentication is enough? If we agree on that it can be implemented easily. -- You are receiving this mail because: You are watching all bug changes.