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

[Bug 18440] New: tmp_holdsqueue should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '22

28 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18440 Bug ID: 18440 Summary: tmp_holdsqueue should have a timestamp Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 If the holds queue builder doesn't run for some reason (cron job disabled, or job crashes), it's not possible to tell when the last entry was made in tmp_holdsqueue. It would be very nice to have a timestamp available for this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 18445] New: Tests in t stumble over Auth's BEGIN block
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '22

19 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18445 Bug ID: 18445 Summary: Tests in t stumble over Auth's BEGIN block Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: gmcharlt(a)gmail.com We should be able to run the tests in t without the database. But if some module loads Auth.pm via C4/Serials or Koha/Virtualshelf directly or indirectly, this will trigger execution of Auth's BEGIN block. This block contains three calls for systempreferences (one from Auth_with_cas). Note that loading Biblio.pm also starts a chain going to Auth.pm. This report changes two use C4::Auth statements into requires. This will prevent or postpone execution of this code. Note also that this will resolve a few failing tests like (Matcher.t and Prices.t) where the schema mock actually was too late and the database was accessed instead of defined fixtures. Along the way we fix a few minor issues in t where database access should be eliminated. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18392] New: Allow importing/ exporting circulation conditions as CSV or spreadsheet
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18392 Bug ID: 18392 Summary: Allow importing/exporting circulation conditions as CSV or spreadsheet Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As our circulation GUI is not perfect (yet) it would be nice if it offered a similar feature to the bibliographic frameworks, allowing to export/import the rules using CSV or spreadsheet files. This would make it much easier to update rules in bulk and keep track of changes to them as you could archive different versions easily too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 17937] New: Adding item description to Twitter Summary
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '22

22 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17937 Bug ID: 17937 Summary: Adding item description to Twitter Summary Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caitlingoodger.student(a)wegc.school.nz QA Contact: testopia(a)bugs.koha-community.org When a user posts a link to an item in their library's catalog on Twitter the description will show in the Twitter card. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 18052] New: Show link to the item for an issue on serial collection page
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '22

19 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18052 Bug ID: 18052 Summary: Show link to the item for an issue on serial collection page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com It would be nice if there was a link to edit the item linked to a specific serial issue from within the serials module. For example, a new column with an 'edit item' link could be added to the serials-collection page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 17814] New: koha-plack --stop should make sure that Plack really stop
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '22

12 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17814 Bug ID: 17814 Summary: koha-plack --stop should make sure that Plack really stop Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org koha-plack --stop doesn't ensure that Plack was really stopped before returning. So in case that koha-plack --stop was quickly follows by koha-plack --start (e.g. logrotate), it could leave Plack in stop state. This is due to koha-plack --start think that Plack was already started, while it actually is being stopped. For me I think this is the cause why I got random Plack stop when logrotate is run. It should be similar to the case of Zebra in Bug #16885, and the solution might be the same: adding "--retry=TERM/30/KILL/5;" to start-stop-daemon command. I just try that on our server and will see if the problem goes away. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 18631] New: Cleanup_database.pl should take an option for modules in action_logs
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '22

11 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18631 Bug ID: 18631 Summary: Cleanup_database.pl should take an option for modules in action_logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Cataloging log is a big one that often needs to be cleaned, other logs can be useful to keep longer, we should take the modules as an option and clear only those specified or exclude specified logs -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 16882] New: Circ restrictions caused by long overdue should be removed when the offending item is returned
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '22

26 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16882 Bug ID: 16882 Summary: Circ restrictions caused by long overdue should be removed when the offending item is returned 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 If a patron is restricted due to a long voerdue and that item is returned, but they have another item overdue by a day their restriction will not be lifted. Some libraries would like to the the restriction tied to the specific item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 15913] New: It should be possible to restrict a problem patron from editing their record or adding comments / tags to records
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15913 Bug ID: 15913 Summary: It should be possible to restrict a problem patron from editing their record or adding comments / tags to records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org A library reported a patron adding harassing comments to the system via editing their account and commenting on records. There is currently no way to restrict this activity for a single patron. Comments and changes are moderated, so only the staff member checking these is harassed, but a goal of 0 people harassed isn't a bad goal. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 18668] New: Add the column localuse to the items table
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '22

20 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18668 Bug ID: 18668 Summary: Add the column localuse to the items table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: jesse(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org new feature: Add the column localuse to the items table. When a localuse is done, increment the localuse column for the item. That way the data is stored with the item like issues and renewals instead of having to do joins to the statistic tables. Thank you, -JesseM -- You are receiving this mail because: You are watching all bug changes.

1 5