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

[Bug 21779] New: Holds history doesn't show where hold placed
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21779 Bug ID: 21779 Summary: Holds history doesn't show where hold placed Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: siobhancottam(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The Holds history tab doesn't show the same information as the modification log e.g. if the reservation was placed in the OPAC or staff client. It is possible to find this information from the log viewer, but not from a patron record modification log as this doesn't show holds at all. This is time-consuming to find the relevant hold if you don't already know the approximate date when the hold was placed. The system log uses the reserve ID as the Object, which is presumably why it doesn't show in the Patron log where their borrowernumber is the Object no. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27314] New: Update default Elastic mapping
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '26

23 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27314 Bug ID: 27314 Summary: Update default Elastic mapping Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: nick(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com As we've been bringing libraries online with Elastic searching, we've run into a handful of changes to the default mappings. I'm filing this bug to remind us to push some of those back into the community defaults. I'll circle back here with details of changes we've made. Anyone else have changes they'd like to see in the community ES mappings? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 21592] New: When adding to basket from a file and using MarcFieldsToOrder items are not added to basket if missing funds
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '26

23 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21592 Bug ID: 21592 Summary: When adding to basket from a file and using MarcFieldsToOrder items are not added to basket if missing funds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Test plan: 1 - Edit the MarcItemFieldsToOrder and MarcFieldsToOrder syspref. For example: MarcItemFieldsToOrder homebranch: 975$a holdingbranch: 975$b itype: 975$c nonpublic_note: 975$d public_note: 975$e loc: 975$f ccode: 975$g price: 975$h replacementprice: 975$i itemcallnumber: 975$j notforloan: 975$m uri: 975$n copyno: 975$o MarcFieldsToOrder price: 975$h 2 - Stage your order file from vendor. (Test file : https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57715 ) 3 - Add to basket from staged file 4 - Values are filled but not budget (ensure you don't have the one in file defined) 5 - Check the box and save 6 - You are returned to empty basket 7 - View the record - items have been created -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27579] New: Add field for creator to Manage staged MARC records
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '26

18 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27579 Bug ID: 27579 Summary: Add field for creator to Manage staged MARC records Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org When viewing the list of .mrc files in Manage staged MARC records it would be helpful to be able to see which logged in user created/imported the batch of records. It would enable staff to contact the person in case there are questions about the content or status of the file. It seems like this could be similar to the 'Author' field that displays for saved reports which shows the name of the Koha user and their patron record number. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27434] New: Task Scheduler should use classes as job types
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '26

18 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27434 Bug ID: 27434 Summary: Task Scheduler should use classes as job types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Task Scheduler Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Rather than maintaining a list of types and going through each case we should use the class as the job type so we can call it directly -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 23919] New: Make ISSN searchable with and without hyphen
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23919 Bug ID: 23919 Summary: Make ISSN searchable with and without hyphen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For the ISBN we have the option to activate search with and without hyphens - but this doesn't work for ISSN. We shoudl make it work there as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56

[Bug 27976] New: Add Granular options to CircConfirmItemParts
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27976 Bug ID: 27976 Summary: Add Granular options to CircConfirmItemParts 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: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be really nice if the "CircConfirmItemParts" added in bug 25261 wasn't all or nothing. We'd like to be able to force confirm on kits, hotspots, and book club kits but not on DVDs and Audiobooks. All of these have materials specified in our catalog. Hitting confirm on each DVD and audio check in and out would make our workflows much slower, but we'd like to be able to do it for some items still. Maybe there could be an option in the item type setup to exclude item types from the confirmation? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 26993] New: Allow StoreLastBorrower to retain up to 2 previous patrons
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26993 Bug ID: 26993 Summary: Allow StoreLastBorrower to retain up to 2 previous patrons 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 14945 Various workflows and circumstances can result in the "last returned by" value stored by StoreLastBorrower getting overwritten sooner than a library might like. For example, a patron may find the item they've checked out was damaged by the previous patron. They put the item in the bookdrop on their way into the library and then alert staff to the damage when they check out their next batch of items. By that time, the damaged item has been checked in, our imaginary patron shows as "last returned by," and we have no record there of who had it previously. We could alleviate this by adding a third option to the StoreLastBorrower system preference, so that one can choose "Do not store," "store 1," or "store 2." This entire feature would still be optional for libraries that don't want to keep this data. Additionally, bug 23260 is adding the ability to clear this data after a period of time using cleanup_database. These factors help mitigate the privacy concerns inherent to the matter. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14945 [Bug 14945] Add the ability to store the last patron to return an item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 84

[Bug 20153] New: Add new column "source" in the authorities pages's result
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '26

15 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20153 Bug ID: 20153 Summary: Add new column "source" in the authorities pages's result Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl hi, It would be nice if we could add a new column in the results page of a search in authority's module.In this new column we could se the subfield 040 $a who show the Organization that performed the original cataloging. With this new column with this new column titled "source", like the column in the z39.50 search, we would not need to go back to the authority record to see if it's a locally created authority or if it's imported. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 28308] New: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28308 Bug ID: 28308 Summary: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Looking at the code below, it seems that on the day an item is due we will only send the DUE notices, predues will not be sent In the advance_notices.pl cron: 276 if ( 0 == $upcoming->{'days_until_due'} ) { 277 # This item is due today. Send an 'item due' message. ... 323 } else { 324 $borrower_preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $upcoming->{'borrowernumber'}, 325 message_name => 'advance_notice' } ); 326 next UPCOMINGITEM unless $borrower_preferences && exists $borrower_preferences->{'days_in_advance'}; 327 next UPCOMINGITEM unless $borrower_preferences->{'days_in_advance'} == $upcoming->{'days_until_due'}; In this case, allowing the user to choose '0' is effectively disabling the notice. I think we need to remove 0 as an option, and uncheck all transports for patrons who have '0' set for days in advance -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26