https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 --- Comment #99 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to David Cook from comment #96)
(In reply to Jonathan Druart from comment #95)
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.
I'm not sure I understand 100% what you're saying. I think that I agree that a high level administrator should be able to manage all/any jobs. So manage_background_jobs.pl probably should have a particular/specific admin permission I would think.
That's how it works already, there is a manage_background_jobs permission. The question is about a "normal" user (without that permission) who enqueued a new job. (In reply to David Cook from comment #97)
I'm finding the number of patches to be a bit intimidating, so I made this little git diff of changed files:
Then squash them locally :)
From a staff interface perspective, it looks like the main things to test are admin/background_jobs.pl and tools/batch_record_modification.pl?
From a sysadmin perspective, it looks like it would be a good idea to test /etc/init.d/koha-common, koha-create, koha-disable, koha-remove, and koha-worker.
I'm not seeing any usage for "koha_worker.pl" or "new_koha_job.pl". Are these dev scripts that should be removed?
"Bug 22417: [DO NOT PUSH] Add simple worker and add_job scripts" Those are for tests and won't be pushed. -- You are receiving this mail because: You are watching all bug changes.