May 2025 - Koha-bugs - lists.koha-community.org

[Bug 37140] New: Add vendor automatically to 952 $e when creating items for serials
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37140 Bug ID: 37140 Summary: Add vendor automatically to 952 $e when creating items for serials Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On receiving a serial in the serials module, it would be helpful to add the id of the vendor automatically to the item In 952 $e (Source of acquisition), if the subscription is set to "create an item record", and the subscription has a vendor. Similar to the acquisition module, where the vendor is already added automatically to the items. To test: 1. If necessary, set 952 $e in the bibliographic framework to visible in the staff interface and the editor. 2. Go to serials 3. Create a subscription with a vendor and the setting “create an item record” and save it. 4. Go to serial collection. 5. Set a serial issue from status “Expected” to “Arrived” 6. The vendor in subfield “e” (Source of acquisition) in the item form is empty. But it would be nice if the vendor was filled in automatically. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 31736] New: Context for translation: "All"
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31736 Bug ID: 31736 Summary: Context for translation: "All" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr "All" is used all over Koha, and refers to different things. In French, those different things have different genders and the "All" must be in that gender ("tous" for "male-gendered" things and "toutes" for "female-gendered" things). In fr-CA-staff-prog, it says "All" is used in these places #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:313 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:380 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/parcel.tt:347 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:121 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:123 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:208 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:216 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:387 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:918 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:939 #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt:45 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:247 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:254 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:261 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/readingrec.tt:57 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:63 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:74 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:86 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:203 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:248 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:263 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/cash_register_stats.tt:111 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/dictionary.tt:116 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:245 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:259 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:887 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1494 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:152 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:156 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:165 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:179 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/checkexpiration.tt:50 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:281 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:415 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:25 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:37 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/additional-contents.tt:135 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/marc_modification_templates.tt:226 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:217 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:219 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:238 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:240 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:270 #: koha-tmpl/intranet-tmpl/prog/en/includes/additional-fields-entry.inc:12 #: koha-tmpl/intranet-tmpl/prog/en/includes/av-build-dropbox.inc:16 #: koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc:247 #: koha-tmpl/intranet-tmpl/prog/en/includes/subscriptions-search.inc:33 #: koha-tmpl/intranet-tmpl/prog/en/includes/str/tinymce_i18n.inc:2 We should add context so that translators know what that "All" refers to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 157

[Bug 29236] New: Allow OPAC News / HTML Customization contents to be set for library groups
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29236 Bug ID: 29236 Summary: Allow OPAC News / HTML Customization contents to be set for library groups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For the content sent to various OPAC pages/fields from the HTML Customizations interface (OPACNavRight, OPACHeader, etc), it would be helpful to be able to set those values for groups of libraries, rather than just individual libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28593] New: Add ability to charge lost fee when applying new lost status when resolving a claim
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 Bug ID: 28593 Summary: Add ability to charge lost fee when applying new lost status when resolving a claim 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: 28271 Bug 28271 added the ability to apply a new lost status when resolving a claim. We should also add the ability to charge a replacement fee. Many libraries do not charge a replacement fee when a claim is generated. If the item is not found within the time period allowed by library policy, then the item is assumed lost, the claim is resolved, and the item is set to lost. At that point, the library would like to charge the patron. As things stand, there is not a way to generate a lost fee tied to that issue_id. You'd have to either create a manual invoice or return the item, check it back out to the patron, and mark it lost again. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28271 [Bug 28271] Add the ability to set a new lost status when a claim is resolved -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 24288] New: Add wording to authorized value interface to indicate valid code length
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24288 Bug ID: 24288 Summary: Add wording to authorized value interface to indicate valid code length Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Several standard authorized values feed into fields that require a single character code (LOST, NOTFORLOAN, DAMAGED, RESTRICTED, WITHDRAWN). It'd be good to have some wording in the authorized value interface that would indicate this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 33905] New: Username and cardnumber should be unique respectively
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33905 Bug ID: 33905 Summary: Username and cardnumber should be unique respectively Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently Koha allows a user to sign in with either their cardnumber or userid Confusion can arise when a user has a username that is another users cardnumber, and vice versa We should check uniqueness across both of these fields. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 38757] New: Adding order from a staged file - "Some required subfields are unset"
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38757 Bug ID: 38757 Summary: Adding order from a staged file - "Some required subfields are unset" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org When ordering from a staged file that contains item data, we have the option to edit or confirm the individual items on the "Select to import" tab, or import all items with identical information from the "Item information" tab. When importing individualized item data from the "Select to import" tab, clicking Save triggers an error: "Some required subfields are unset". Setting the Koha item type in the "Item information" tab fixes this error - but it shouldn't be necessary to set the item type in that tab if all items in the "Select to import" tab already have an item type specified. To replicate: 1. Go to Acquisitions and find or open a basket 2. Click Add to basket 3. Click Add from new file 4. Upload a MARC file containing item data 5. When the upload completes, click "Add to basket" 6. In the "Select to import" tab that comes up by default, check the checkbox next to one or more titles in the file --> This will expand the item data for those titles 7. Look over the item data, and confirm that all items have a homebranch, holdingbranch, and item type defined 8. Click "Save" --> An error pops up: "Some required subfields are unset" 9. Navigate to the "Item information" tab 10. Select a value for y - Koha item type 11. Click "Save" again --> The orders are imported successfully -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36801] New: Allow un-resolving of a catalog concern
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36801 Bug ID: 36801 Summary: Allow un-resolving of a catalog concern 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We didn't allow for re-opening a resolved catalog concern before, but with the introduction of the update status's I think we managed to change the logic a bit and the 'Update' button now displays. This effectively allows for re-opening a resolved ticket; However, the actual ticket state isn't properly updated and should be so the new state is properly reflected in the display table and filtering options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 21889] New: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21889 Bug ID: 21889 Summary: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently only Purchase Suggestions made by patrons through the OPAC are the only suggestions counted in the system preference MaxOpenSuggestions. It would be nice if this system preference also connected to the staff client, so a purchase suggestion done on the patrons account by staff alerted the staff that the patron already had the maximum number of purchase suggestion allowed. At this time, even if a patron has maxed out the number of open purchase suggestions on the OPAC, a staff member can still enter more purchase suggestions for that patron through the staff client without knowledge of the maxopensuggestions being reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 39054] New: a need to distinguish between manual bibliographic record modifications and those being a consequence of authority modification
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39054 Bug ID: 39054 Summary: a need to distinguish between manual bibliographic record modifications and those being a consequence of authority modification Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Now in action_logs, Koha does not distinguish between manual bibliographic record modifications and those being a consequence of authority modification. Both are logged in the same way: module: CATALOGUING ; operation: MODIFY ; interface: intranet. IMO it would be helpful to be able to distinguish this two cases. (For instance to be able to evaluate a librarian's 'koha' in the cataloguing process: a single action of modification of one authority record launching a modification of, say, 100 bibliographic records does not equal to manual modification of 100 bibliographic records. Also, if we trace issues in bibliographic records after modification being performed and want librarians to correct themselves, a biblio modification being a consequence of an authority modification should not be taken into account. Etc.) Comment are welcome. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38