Bug 25647 - Allow hold notifications to be disabled separately from the process_message_queue
Summary: Allow hold notifications to be disabled separately from the process_message_q...
Status: RESOLVED DUPLICATE of bug 25310
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-01 19:58 UTC by Liz Rea
Modified: 2020-06-02 06:39 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liz Rea 2020-06-01 19:58:41 UTC
During these library closures, it has been apparent that it would be good to allow the hold notices to be disabled separately from the process message queue. 

A common scenario is a library wants to process holds but does not want hold notifications to go out. They also want to have overdues and advanced due notices to go out. 

I know we can already (or very soon) run the message queue enabled for different branches, but I feel there needs to be a way to allow the libraries to be able to manage what is on or off from the interface, and not with a cron flag as it is done currently.

I've thought of a few ways we might do this

- through the enhanced messaging preferences (allow an override per patron category or branch for these optional notices) 

- as a different set of flags on the process_message_queue cron

or something else entirely.
Comment 1 Katrin Fischer 2020-06-02 06:39:37 UTC

*** This bug has been marked as a duplicate of bug 25310 ***