February 2020 - Koha-bugs - lists.koha-community.org

[Bug 23456] New: Show 'date last seen' for items requested in Holds Queue
by bugzilla-daemon＠bugs.koha-community.org 05 May '26

05 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23456 Bug ID: 23456 Summary: Show 'date last seen' for items requested in Holds Queue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be very useful to view the contents of items.datelastseen in the Holds Queue. Ideally, this information would be presented in its own column so it could be sorted. Some fields from the items table are already called in the itemsloop, so it appears that the tables are already joined (e.g. items.barcode is already presented in the Holds Queue). This is something that our staff request repeatedly as it would help them to prioritise their searches in busy libraries (where the Holds Queue can run to hundreds of items). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 20747] New: Allow LocalHoldsPriority to fill by hierarchical groups system rather than individual library
by bugzilla-daemon＠bugs.koha-community.org 04 May '26

04 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20747 Bug ID: 20747 Summary: Allow LocalHoldsPriority to fill by hierarchical groups system rather than individual library Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be great if the LocalHoldsPriority could be used within a district in a consortium. >>Christopher expressed concern, adding on “grouping” – some libraries may not >>want to be effected. Typically this is all or nothing or on or off. Example, >>the circulation of Mobile Hotspots; hotspots are popular outside of CDA but CDA >>patrons get priority, Rathdrum is pushed down. Consider an “Item type” or “Item >>level” opt out which would be similar to how suppression works. If the >>modification increased features and flexibility, there may be more interest from >>the larger group in supporting the enhancement. Group structure for settings, a >>hierarchy based system, and refinement is needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 86

[Bug 22240] New: Add possibility to specify a category of patron in calendar
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22240 Bug ID: 22240 Summary: Add possibility to specify a category of patron in calendar Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Hi, Currently when we add a closing day in the calendar we can not specify a particular patron category. Which means, this day of closure affects all types of patrons of the library and at the same time the circulation rules. It would be nice if when we add a closing day, to have the possibility to specify a category of patrons that would be subject to this closing day. Like that, the rest of the patrons catgory are not concerned by this limitation. It could be an additional option in the page to choose the type of closing day where you would have access to the list of types of users in the library. Thanks, Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24444] New: Enfore mutual exclusivity in Stockrotation and Rotating Collections
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24444 Bug ID: 24444 Summary: Enfore mutual exclusivity in Stockrotation and Rotating Collections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com An item should not be able to belong to both a rotating collection and a stock rotation rota at the same time. We should enforce this by warning and preventing the end user from taking such action. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 23088] New: Stockrotation full_report should use 'notices'
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23088 Bug ID: 23088 Summary: Stockrotation full_report should use 'notices' 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- The stockrotation cronjob allows for two different types of report. One of those reports is plumbed in to using the SR_SLIP from the 'notices' system, but the other reports 'full' is hard coded in the script. We should add a second SR_REPORT slip to the notices system to use for this full report to allow for easier translations etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24035] New: When recording local use, there is no alert for holds
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24035 Bug ID: 24035 Summary: When recording local use, there is no alert for holds 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com One way of recording local use is through a statistical patron. Checking an item out to a statistical patron records a local use but does not actually check the item out. However, if the item is on hold, there is no indication that it is so, since the item doesn't go through the checkout process. But since the staff is already processing the item to scan it for local use, I feel like it would be logical to alert them that there is a hold on this item. To reproduce: 1- Create a statistical patron category 1.1- Go to Administration > Patron categories 1.2- Create a new patron category 1.3- Fill in the code, description and expiry date 1.4- In the 'Category type' field, choose 'Statistical' 1.5- Save 2- Create a patron of that category 3- Place a hold on an item (for another patron) 4- Check out the item to the statistical patron => It says 'Local use recorded' but there is no pop-up saying the item is on hold -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 20844] New: Reset a hold when it is missing after allocation
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20844 Bug ID: 20844 Summary: Reset a hold when it is missing after allocation Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There currently is no simple way to 'deallocate' a hold if it has gone missing after it is allocated to a patron but before they collect it. This enhancement would work as follows: 1. item is allocated 2. item cannot be located when patron tries to collect it 3. staff member marks item as Lost 4. if hold was originally a bib-level hold, hold reverts from being specific to the missing item, back to a bib-level hold with priority 1. 5. if hold was originally item-level, staff member gets an alert asking whether to cancel or retain the hold 6. (optionally?) a 'lost hold' notice is queued to be sent to the patron This bug is related to the original description of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287#c32 and also to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 To do it properly, it may require a couple of new settings, something like: LostBibLevelHoldsRevert SendLostHoldNotices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 150

[Bug 23998] New: Messages REST API
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23998 Bug ID: 23998 Summary: Messages REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi Expose messages table via REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 17772] New: Allow to sort lists by date the record was created
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17772 Bug ID: 17772 Summary: Allow to sort lists by date the record was created Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Lists in OPAC and staff can be sorted by different fields. It would be nice if we could offer 'date created' as an additional option for sorting. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 23849] New: Update the list of sysprefs to share with Hea
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23849 Bug ID: 23849 Summary: Update the list of sysprefs to share with Hea Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have a lot of sysprefs that are not recorded in Hea. We lack a process to keep the list up-to-date. We are going to have an updated list for 19.11. For next releases it should be a new post release task (https://wiki.koha-community.org/wiki/Post_major_release_tasks) This bug report could be reused for the next releases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81