June 2017 - Koha-bugs - lists.koha-community.org

[Bug 15831] New: Can't override renew limit by submitting a barcode in checkout with AllowRenewalLimitOverride on
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15831 Bug ID: 15831 Summary: Can't override renew limit by submitting a barcode in checkout with AllowRenewalLimitOverride on Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If I have AllowRenewalLimitOverride set to "Allow," I should be able to scan a barcode in checkout and be prompted to override the renewal limit. That's how it works on the renewal page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18816] New: Make CataloguingLog work in production by preventing circulation from spamming the log
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18816 Bug ID: 18816 Summary: Make CataloguingLog work in production by preventing circulation from spamming the log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference CataloguingLog is not recommended for use in production. This is do to the fact that every checkin and checkout generates one or more log entires. This seems to be not only bad behavior, but unnecessary and outside the needs of CataloguingLog as we have CirculationLog. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 16544] New: Changes to circ rules should be logged.
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '26

13 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16544 Bug ID: 16544 Summary: Changes to circ rules should be logged. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At present, changes to circulation rules are not logged. This means that there is no way to determine what circulation rules were in effect at a given time, which makes historical trouble-shooting impossible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 17471] New: Borrower Previously Checked Out: Date of last checkout
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '26

12 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17471 Bug ID: 17471 Summary: Borrower Previously Checked Out: Date of last checkout 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When the dialog with previous checkout confirmation appers, there should be displayed the date of last checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18450] New: Renew in header bypasses hold block and renewal limits
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '26

12 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18450 Bug ID: 18450 Summary: Renew in header bypasses hold block and renewal limits Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When you renew an item on hold, it allows you to bypass the hold, even if you don't allow it elsewhere. It also bypasses renewal limits set in Circulation Rules. Does not honor AllowRenewalLimitOverride preference if set to Don't allow. Does not honor AllowRenewalIfOtherItemsAvailable if set to Don't allow. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 16122] New: Item record needs to keep Local Use count
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16122 Bug ID: 16122 Summary: Item record needs to keep Local Use count 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Like the "issues" field in the items table, there should be a field for "local_use" to keep the count of local uses. While this information is kept in the statistics table, it is a task to acquire, and if a library wants to keep bloat down on their tables, the statistics are pruned on a regular schedule, which means loss of valuable data. This counter would keep that valuable information in one field in each item record, rather than having a separate field for each instance in the statistics table. Unless it is vital to someone to know the exact moment a local use occurred, I am suggesting that this piece of information not be recorded in the statistics table any longer. This would significantly reduce the growth of the statistics table in general. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 164

[Bug 18397] New: Sent notices for...: Display email address ( including which field it's taken from)
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '26

10 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18397 Bug ID: 18397 Summary: Sent notices for...: Display email address (including which field it's taken from) 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Display in Home > Patrons > Sent notices for... the email address and the field where it is taken from. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 17120] New: Specify number of rows per page in report and initial run
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '26

09 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17120 Bug ID: 17120 Summary: Specify number of rows per page in report and initial run Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think we could enhance reports so that the &limit= parameter could be initially set with the report settings and stored in a field in the table. I also think we could have the drop down available on the parameters page when running the report the first time. If you have a report you know that would run well and could be completely shown with more rows, why not have the option to initially set it differently than the default? The LIMIT command in SQL is okay and works for actually limiting the total number of results, but does weird things if you specify a number larger than 20. The results still span multiple pages, plus it doesn't give you options while running like this would. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 18783] New: Allow automatic claims for serials
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18783 Bug ID: 18783 Summary: Allow automatic claims for serials Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Serials Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 16631] New: Show groups/categories of reports to authorized staff
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '26

03 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16631 Bug ID: 16631 Summary: Show groups/categories of reports to authorized staff Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful to have reports that are specific groups/categories to be authorized under the reports permissions in a patron account. Not everyone wants to see everyone else's reports, some are similar but are not. Some are for superlibrarians to test, and are not ready for use. It would be great if we could specify groups and even subgroups in the permissions that the staff could access, or specify all groups. All groups should be the norm for a superlibrarian. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 301