October 2022 - Koha-bugs - lists.koha-community.org

[Bug 19540] New: opac-reserve does not correctly warn of too_much reserves
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19540 Bug ID: 19540 Summary: opac-reserve does not correctly warn of too_much reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When attempting to place more holds than allowed, opac-reserve.pl only checks against the SysPref 'maxreserves' and not the issuingrules 'holdsallowed'. If the issuing rule's limitation is lower than maxreserve, the opac-reserve page shows a message saying you cannot place any more holds but the explanatory message does not show. To reproduce: 0) Set MaxReserve to a high value (50 is default); 1) Set an issuing rule's "Holds allowed" to a low number (1 or 2); 2) Place as many holds as you can (for the corresponding (categorycode, itype, branchcode, etc). When you reach the maximum allowed by the issuing rule, you'll see a message telling you cannot place any more holds, but the explanatory message saying that you cannot place more than %d holds will not show. (It will show "No items available instead". Bug is present on 16.05 and master -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 31970] New: background_jobs_purge.pl to purge background jobs queue
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31970 Bug ID: 31970 Summary: background_jobs_purge.pl to purge background jobs queue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: frederic(a)tamil.fr QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 31980] New: Allow for editing of patron message
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31980 Bug ID: 31980 Summary: Allow for editing of patron message Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In messages.message there is not a way to edit a message once it has been created. The only option is to either add a separate message referring to a previous message, or delete the message and create a new one with the content. It would be a great benefit to be able to edit a message to add supplemental/updated info within the same message. Ideally, the original creation info (borrower, date, branch) would be kept, and another set of data (borrower, date, branch) added when the message is added on to. For instance, original message is: 10/22/2022 East Library ( bwssupport ) "Please check address - mail was returned" and when I edit the message, it now says 10/22/2022 East Library ( bwssupport ) "Please check address - mail was returned" 10/25/2022 East Library ( djones ) "Spoke to patron - they will bring in updated info" all within one message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31978] New: A cron job is needed to clean out background jobs/tasks
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31978 Bug ID: 31978 Summary: A cron job is needed to clean out background jobs/tasks Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org Our consortium has about 21 libraries that use our Koha install. In just two months, we have logged almost 2,000 background jobs. It would be nice to have a cron job that will automatically clear these out periodically. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31977] New: Make Item Search result sortable by multiple columns
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31977 Bug ID: 31977 Summary: Make Item Search result sortable by multiple columns Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be really helpful to allow sorting by multiple columns on the item search results page. Right now, you can only sort by one column at a time. It would be a great addition to be able to sort for instance, by call number, then click on the data column and have a secondary sort on that column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 14180] Make "Always show checkouts immediately" a global setting
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14180 --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Marie-Luce Laflamme from comment #15) > (In reply to Katrin Fischer from comment #14) > > (In reply to Marie-Luce Laflamme from comment #13) > > > The IntranetUserJS syspref work around isn't working in Koha 22.05+ version. > > > > The handling for cookies has changed, this appears to work on master: > > > > $(document).ready(function() { > > > > if (typeof script !== 'undefined' && > > Cookies.get("issues-table-load-immediately-" + script) !== "true") { > > Cookies.set("issues-table-load-immediately-" + script, true, { expires: > > 365, sameSite: 'Lax' }); > > } > > > > }); > > > Your quick fix works well in 22.05 and the latest master version. > > Thanks Kathrin Thx for the feedback, happy it helped! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31979] New: Allow formatting / line breaks when editing return_claims.notes
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31979 Bug ID: 31979 Summary: Allow formatting / line breaks when editing return_claims.notes Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When editing notes in the Claim Return function, line breaks are not maintained - all notes run together into one note. With how Claim Return notes are used (such as updating the note that a shelf check has been added) these notes need to be visibly separate from each other. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14180] Make "Always show checkouts immediately" a global setting
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14180 --- Comment #15 from Marie-Luce Laflamme <marie-luce.laflamme(a)inlibro.com> --- (In reply to Katrin Fischer from comment #14) > (In reply to Marie-Luce Laflamme from comment #13) > > The IntranetUserJS syspref work around isn't working in Koha 22.05+ version. > > The handling for cookies has changed, this appears to work on master: > > $(document).ready(function() { > > if (typeof script !== 'undefined' && > Cookies.get("issues-table-load-immediately-" + script) !== "true") { > Cookies.set("issues-table-load-immediately-" + script, true, { expires: > 365, sameSite: 'Lax' }); > } > > }); Your quick fix works well in 22.05 and the latest master version. Thanks Kathrin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31975] New: Add Item Search to table settings
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31975 Bug ID: 31975 Summary: Add Item Search to table settings Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With all of the incredibly useful info on the item search, being able to configure the columns would be a great addition! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27086] New: Add a both/most restrictive option for ReservesControlBranch
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27086 Bug ID: 27086 Summary: Add a both/most restrictive option for ReservesControlBranch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries would like to be able to check both a patron's branch, and an items branch when determining if an item can be held. This is related to reciprocal borrowing, where one library does not allow holds on dvds from other libraries, but other libraries do. They want the home library's rule to affect their patrons when placing holds on DVDs from other libraries In this scenario we would check the rules based on both settings, using the most restrictive rule found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4