https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #96 from David Cook <dc...@prosentient.com.au> --- (In reply to Jonathan Druart from comment #95) > What is the "source module"? > Oh I mean the module where the source of the call is made. So in this case, "Staged MARC for Import" would be in the Tools module. But in the Circulation module you could upload an Offline Circulation module, and queue up a job to do that import in the background. It seems to me that the person should be able to review their job within the module that they made it. > 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. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
