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

[Bug 18948] New: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18948 Bug ID: 18948 Summary: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This patchset aims to add the ability to leverage the ES alias feature during a reindex - when doing a full reindex or a deletion the indexer will look for an existing index under the alias - if not found it will create a new one, if found it will index into a new index and point the alias there when done and then delete the old index. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 25825] New: Allow Claim Return function to be controlled by permissions
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25825 Bug ID: 25825 Summary: Allow Claim Return function to be controlled by permissions Change sponsored?: --- Product: Koha Version: 19.11 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 It would be helpful to have a way to control which users are able to initiate and resolve a claim return. Some libraries will only want certain levels of staff to be able to initiate the Claim Return, and likewise, only certain staff should be able to resolve it. Perhaps a permission for each of those functions? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 36913] New: Booking should take non-for-loan into account
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36913 Bug ID: 36913 Summary: Booking should take non-for-loan into account Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: data-27FC05A3CB97(a)office-dateien.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It appears that bookings are placed on items that are marked as not for loan. This seems to be independent whether holds can be placed on an item or not (positive or negative NOT_LOAN value). There should be an option to prevent this, ideally by having a way to specify which NOT_LOAN values are acceptable for bookings (similar to SkipHoldTrapOnNotForLoanValue). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33523] New: Hold Queue targets items on record level holds that should not fill the hold
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33523 Bug ID: 33523 Summary: Hold Queue targets items on record level holds that should not fill the hold 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Holds queue doesn't check if a branch's item can fill the hold if at least one item is available on the record for a bib level hold To recreate: • Have ReservesControlBranch set to "item's home library" • Have at least 2 libraries. • Set the circulation rules so that a patron type can place holds on an item type at library A • Set the circulation rules so that the same patron type cannot place holds on or have any checkouts on the same item type at library B • Make a record with at least 2 items, one at library A and one at library B. • Place a bib level hold for a patron matching the patron type in the rules • Run holds to pull for both branches • The item should only show on Library A's list, but it also shows on library B. Library B doesn't allow checkout of those items for that patron type. The same thing also happens if there are separate item types on the same record, such as a public copy and a staff copy. The staff copy will try to fill the hold even though it can only be held and loaned by staff. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 33070] New: Get rid of Koha::Patron->can_edit_item and use can_edit_item_from instead
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33070 Bug ID: 33070 Summary: Get rid of Koha::Patron->can_edit_item and use can_edit_item_from instead Change sponsored?: --- Product: Koha Version: master 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 20256 introduced a pattern we are trying to avoid for a long time now (old patchset). It should be refactored and cleaned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 23898] New: New data to share on HEA
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23898 Bug ID: 23898 Summary: New data to share on HEA Change sponsored?: --- Product: Koha Version: master 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: paul.poulain(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some ideas of thing that could be shared on HEA for statistics purposes: - adding some statistics like "intranetuserjs yes/no" => yes if there's something, no if it's empty ? (intranetuserjs, opacuserjs, opac & intranet css, opacheader, opacnav, opacbottom). - For sysprefs *XSLT* => we could send "empty/default/local". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 30552] New: Add a way to import circulation rules
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30552 Bug ID: 30552 Summary: Add a way to import circulation rules 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 18392 added a method for exporting the circ table, however, that bug originally requested both import/export - opening this to allow import to be explored in the future -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 32581] New: Update dateexpiry on categorycode change
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32581 Bug ID: 32581 Summary: Update dateexpiry on categorycode change Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you change a patron's category code, nothing checks whether their existing dateexpiry is valid for their category. An immediate renewal will correct this, but without that step, you could have someone move from a category with longer enrollment into a shorter enrollment period without anything prompting a check if that dateexpiry is still valid. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 25384] New: Label maker font list is not configurable
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384 Bug ID: 25384 Summary: Label maker font list is not configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The label maker font list is hard-coded to 12 arbitrary choices. It would be better if we could configure the font choices in the user interface (since we can already configure the truetype font files in koha-conf.xml). -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 36741] New: AUTO_RENEWALS_DGST should skip auto_too_soon
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36741 Bug ID: 36741 Summary: AUTO_RENEWALS_DGST should skip auto_too_soon Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I think it's debateable that auto_too_soon items should show up in the AUTO_RENEWALS_DGST at all, but I can think of reasons why they would be useful to show (you might want to show which items weren't renewed because it was too soon). But at the moment, the AUTO_RENEWALS_DGST doesn't account for them. It just prints out the title and barcode, which looks ridiculous. We need a default. Either to skip auto_too_soon in that loop, or to say that it's too soon for it to be renewed. I'm in favour of the former. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27