September 2024 - Koha-bugs - lists.koha-community.org

[Bug 25824] New: DecreaseLoanHighHolds.t is still failing randomly 2
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25824 Bug ID: 25824 Summary: DecreaseLoanHighHolds.t is still failing randomly 2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org After 188 local run I could reproduce on 19.05.x the failure that happening on this build: https://jenkins.koha-community.org/view/19.05/job/Koha_19.05_D9/229/console… t/db_dependent/DecreaseLoanHighHolds.t .. 2/17 # Failed test 'Static mode should exceed threshold' # at t/db_dependent/DecreaseLoanHighHolds.t line 131. # got: '0' # expected: '1' # Failed test 'Should have duration of 1' # at t/db_dependent/DecreaseLoanHighHolds.t line 133. # got: '0' # expected: '1' # Failed test 'due_date should be a DateTime object' # at t/db_dependent/DecreaseLoanHighHolds.t line 134. # got: '' # expected: 'DateTime' Can't call method "hour" on an undefined value at t/db_dependent/DecreaseLoanHighHolds.t line 137. # Looks like your test exited with 11 just after 5. t/db_dependent/DecreaseLoanHighHolds.t .. Dubious, test returned 11 (wstat 2816, 0xb00) It was like 30 min, so not so hard to reproduce (assuming it wasn't huge luck) Happens also in Ubuntu 18.04 for 19.05.x branch. (if that can help) https://jenkins.koha-community.org/job/Koha_19.05_U18/236/consoleText It's the second time a few days. It's good that it's not a rare issue. -- You are receiving this mail because: You are watching all bug changes.

1 8

[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 34472] New: Template Toolkit reference guide needed
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34472 Bug ID: 34472 Summary: Template Toolkit reference guide needed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org There are no resources that I've been able to find that clearly layout what we can use from Template Toolkit in our notices and slips. We have https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_M… and https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit but neither clearly layout what we can use, and in which slips. These are more generalized guidelines, but if I am referencing some specific elements, it's a guessing game. And I keep coming across things to use I never heard of before, not mentioned anywhere. It would really be helpful if a wiki guide were put together to make this much clearer than it is right now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 31046] New: Floating Rules Based on Collection/Shelving Location
by bugzilla-daemon＠bugs.koha-community.org 01 May '26

01 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31046 Bug ID: 31046 Summary: Floating Rules Based on Collection/Shelving Location Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: daniel.gaghan(a)pueblolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com PCCLD would like an option for floating rules to be based on the items shelving location or collection. This is how it would work. 1. A system preference allows for an Authorized Value/Shelfing Location or Collection to restrict floating. 2. The Western Research (Library A) location is added to the system preference and all material with the value does not float. 3. Item is cataloged with the Western Research shelving location. 4. Item is checked-out by a user at Library A. 5. The item is returned to Library B. 5. A message appears in Koha stating the item needs to return to Library A because it does not float. -Daniel -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

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

01 May '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 36013] New: update_totalissues.pl should not log
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36013 Bug ID: 36013 Summary: update_totalissues.pl should not log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Even when CataloguingLog is on, misc/cronjobs/update_totalissues.pl should not log the changes. It is useless and takes database space. Do like bulkmarcimport.pl : https://git.koha-community.org/Koha-community/Koha/src/branch/23.11.x/misc/… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 35957] New: Does Serial module still allow saving 0000-00-00 in database?
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35957 Bug ID: 35957 Summary: Does Serial module still allow saving 0000-00-00 in database? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing two issues in 22.11 with invalid/empty date fields: [1] Exception 'Koha::Exceptions::WrongParameter' thrown 'Invalid date '00-1-11-30' passed to output_pref' Crash in output_pref comes from serials/subscription-add.pl line 405 $nextacquidate = $nextacquidate ? output_pref( { str => $nextacquidate, dateonly => 1, dateformat => 'iso' } ) : $firstacquidate; So it received a 0000-00-00. [2] Receive step on serial collection. Save issue without filling dates: | 9531 | 156662 | 318 | No. 12 | 11 | 0 | 0 | 1 | 0000-00-00 | | 0000-00-00 | | NULL | 0 | NULL | Planned and publisheddate were NULL but are now 0000-00-00. Did not check master. Probably still the same? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 37638] New: Link permissions to entry in the manual
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37638 Bug ID: 37638 Summary: Link permissions to entry in the manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lauren_denny(a)sil.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Similar to bug 37624, create a link by the permission that takes you to the manual. If applicable, it would also be helpful to put a note by the permission if a system preference is required. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[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