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

[Bug 14167] Add Koha::Logger based on Log4perl
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14167 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |12855 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 [Bug 12855] Scripts that support logging should enable logging by default -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12855] Scripts that support logging should enable logging by default
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |14167 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14167 [Bug 14167] Add Koha::Logger based on Log4perl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15400] Display patron age in useful places
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15400 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #29 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Josef, this works nicely, with one exception: on the guarantors search the number doesn't show, only ( years). As there has been some controversy about showing this information - could you consider wrapping a span with a class around the years part? Thx! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10215] Increase the size of opacnote and librariannote for table subscriptionhistory
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10215 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off --- Comment #20 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Patch corrected and re-based, back to SO. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10215] Increase the size of opacnote and librariannote for table subscriptionhistory
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10215 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #85400|0 |1 is obsolete| | --- Comment #19 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Created attachment 87705 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=87705&action=ed… Bug 10215: Increase the size of opacnote and librariannote for table subscriptionhistory We have librarians that are regularly hitting the maximum number of characters for the note fields in subscription history. They would like to be able to store at least 1000 characters here. Converting the varchar(150) to text should do it. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 3) Add public and private notes to a subscription history entry where each note is greater than 150 characters. 4) Save and view the notes, the notes should not be truncated. Rescued-by: Martin Renvoize <martin.renvoize(a)ptfs-europe.com> Signed-off-by: Owen Leonard <oleonard(a)myacpl.org> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22668] New: Use select2 styled pull down for cities/town pull down in patron account
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22668 Bug ID: 22668 Summary: Use select2 styled pull down for cities/town pull down in patron account 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: 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 Target Milestone: --- The Select2 library gives you nice search options for the pull downs and is currently used only in the item form. I think it would be nice to use it on other 'long' pull downs too and the cities/town pull down might be a good candidate. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 22670] New: Prevent changing of barcode on checked out items
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22670 Bug ID: 22670 Summary: Prevent changing of barcode on checked out items 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: stina.hallin(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- It is possible to change barcode on a checked out item. This will cause problems when handling the item later. Suggestion is to add an option (syspref?) for protecting certain fields in the edit item form. There might be other fields that other libraries want to protect from altering on checked out items. Normally we don't edit checked out items but when you have many items on one bib, it's easy to make a mistake and end up on the wrong item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 9805] Lost items are un-lost if returned, but not if renewed
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9805 --- Comment #57 from SiobhanC <siobhancottam(a)gmail.com> --- Katrin's comment: Maybe it would make sense to differentiate behaviour for long overdue and lost by patron? Yes, this is what I would like to see. I agree that 'lost by patron' items shouldn't be able to be renewed. However, for long overdue items that are auto-changed to lost (to enable us to easily identify them for invoicing) it would be good if they can have the 'not returned' status removed at the point of renewal. If this status isn't removed then the user doesn't receive notices. This would be a much bigger change, but could a new status category of overdue be introduced? Then the differentiation between overdue/lost would be easier. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6759] Use a different account type for account renewals than for new accounts
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6759 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs(a)lists.koha-commun |martin.renvoize@ptfs-europe |ity.org |.com -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 6759] Use a different account type for account renewals than for new accounts
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '19

10 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6759 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@ptfs-europe | |.com -- You are receiving this mail because: You are watching all bug changes.

1 0