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

[Bug 18925] New: Move maxissueqty and maxonsiteissueqty to circulation_rules
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18925 Bug ID: 18925 Summary: Move maxissueqty and maxonsiteissueqty to circulation_rules 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 18887 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18887 [Bug 18887] Introduce new table 'circulation_rules', use for 'max_holds' rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 171

[Bug 18928] New: Move holdallowed, hold_fulfillment_policy, returnbranch to circulation_rules
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18928 Bug ID: 18928 Summary: Move holdallowed, hold_fulfillment_policy, returnbranch to circulation_rules 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 18925 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18925 [Bug 18925] Move maxissueqty and maxonsiteissueqty to circulation_rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 171

[Bug 18887] New: Introduce new table 'circulation_rules', use for ' max_holds' rules
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18887 Bug ID: 18887 Summary: Introduce new table 'circulation_rules', use for 'max_holds' rules 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 18886 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18886 [Bug 18886] Restructure storage of circulation rules to reduce complexity and enable increased flexiblity -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 168

[Bug 22847] New: Specific circ rule by patron category is displaying the default (or not displaying)
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22847 Bug ID: 22847 Summary: Specific circ rule by patron category is displaying the default (or not displaying) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: critical Priority: P5 - low Component: System Administration Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 18887, 18925 Target Milestone: --- There are several things going wrong on the circulation rules screen. The global rule is displayed for specific libraries (even if the rule does not exist for the library), and max_holds is always blank. I have trouble finding the root of the issue, but I will propose a patch to fix both problem. Certainly a mismatch between bug 18887 and bug 18925. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18887 [Bug 18887] Introduce new table 'circulation_rules', use for 'max_holds' rules https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18925 [Bug 18925] Move maxissueqty and maxonsiteissueqty to circulation_rules -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 24260] New: REST Self Registration
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

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

1 4

[Bug 16207] New: Incorporate circulation and fine rules for library groups
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16207 Bug ID: 16207 Summary: Incorporate circulation and fine rules for library groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I think we could simplify circulation and fine rules by incorporating library groups into the mix. For example, I have 27 libraries, and 8 of them follow the same set of rules that are different from the defaults. So, what if instead of cloning these special rules to 8 different libraries (and who knows how many other duplicated sets of rules there are), we defined a set of rules for a library group. If the library is part of that group, it goes by those rules. I don't know if we want to use the same library groups that are already defined in the libraries and groups, or if we want to create a unique Circ rule group. Because, there is always the chance that one or more of the libraries in the 8 that are grouped together by affiliation or region could have a slightly different set of rules. However, I think rules by groups would make managing rules far less complicated than managing groups of cloned rules. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 18327] New: Reception date when receiving multiple issues for a subscription is not the good one
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18327 Bug ID: 18327 Summary: Reception date when receiving multiple issues for a subscription is not the good one Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When receiving several issues for a subscription (Serials > Serial collection > Multi receiving), the reception date is identical to the publication date instead of being the today date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 23731] New: Staff & OPAC both will display the DDC call number in XSLT but can't display the LC call number
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '25

16 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23731 Bug ID: 23731 Summary: Staff & OPAC both will display the DDC call number in XSLT but can't display the LC call number Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 93597 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=93597&action=ed… staff view When looking at the display of the Bib record in both the staff and OPAC, the DDC number will display by default. However, there is no way for an LC number to display. It would be nice if they both displayed and the library could choose to hide one or both. Currently, it appears that it is displaying the 082 and 084, we would like to see it also display the 090 or 050 (or both) by default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 24909] New: Add public route to get a bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '25

16 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24909 Bug ID: 24909 Summary: Add public route to get a bibliographic record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 22456] New: Customers Cancelling their Pending Holds
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '25

16 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22456 Bug ID: 22456 Summary: Customers Cancelling their Pending Holds Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Good morning! I'm not sure if I should have piggybacked this off of the previous ticket, but I'd like to open the discussion on bug 18856 again. We'd like the ability to have patrons cancel their holds once they have been pulled by staff and are awaiting pick up. Our previous catalogue (Bibliocommons) allowed the cancellation of holds once it as captured. This feature was well like and used by our patrons who had determined they didn't need/want the item any longer. This gave the perception that they were freeing up the item for the next person. We have fielded a number of grumpy comments since our migration about the inability to perform this functionality. >From my perspective, if we're allowing patrons to place holds and cancel them before they're captured, we should offer the ability to cancel them up until they're picked up. At the very least, this should be a system option to allow the Library to choose whether they'd like to enable this functionality. Even if the implemented functionality is a placebo for the user ... offer them the ability to cancel the hold and have it remove from their account. As long as optically it appears they've cancelled the hold, there is no harm. If desired, a report could be run to allow staff to pull those items from the shelf if needed. I'm more than happy to elaborate if needed on this, but I feel that this is a feature that is currently missing from Koha that would be a boon to customer service. Thanks Christofer -- You are receiving this mail because: You are watching all bug changes.

1 165