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

[Bug 30802] New: numReturnedItemsToShow doesn't show more than 20 items on the return screen
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30802 Bug ID: 30802 Summary: numReturnedItemsToShow doesn't show more than 20 items on the return screen 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference numReturnedItemsToShow says "show the XX last returned items on the checkin screen". The default value is 20. If you put a value < 20, it affects the returns.pl table. But if you put a value > 20 in the syspref, the table on returns.pl shows a maximum of 21 items. To test: 1- Make lots of checkouts, at least like 40 (I used the batchCheckouts feature) 2- Go to Circulation > Check in 3- Return 21 items The last 20 items returned will be displayed 4- Change numReturnedItemsToShow to 50 5- Return a couple more items Only the last 21 returned items are displayed 6- Change numReturnedItemsToShow to 10 7- Return a couple more items Only the last 10 returned items are displayed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #195 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142903 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142903&action=e… Bug 8367: (follow-up) Remove unnecessary code and atomic update -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133094|0 |1 is obsolete| | --- Comment #194 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142902 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142902&action=e… Bug 8367: (follow-up) Fix tests Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133093|0 |1 is obsolete| | --- Comment #193 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142901 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142901&action=e… Bug 8367: (follow-up) Remove pickup delay message from OPAC It adds unnecessary complexity and information. Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133092|0 |1 is obsolete| | --- Comment #192 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142900 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142900&action=e… Bug 8367: (follow-up) Fix pickup delay text on OPAC and other bits Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133091|0 |1 is obsolete| | --- Comment #191 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142899 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142899&action=e… Bug 8367: Make database update idempotent (across different MariaDB versions) The previous query seemed to work on MariaDB 10.1.48 (used by koha-testing-docker), but it didn't work on MariaDB 10.3.29 (default in Debian 10 as of this writing), but this patched query works on both indempotently. Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133090|0 |1 is obsolete| | --- Comment #190 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142898 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142898&action=e… Bug 8367: Make database update idempotent Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #133089|0 |1 is obsolete| | --- Comment #189 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 142897 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142897&action=e… Bug 8367: Add holds_pickup_period circulation rule So that pickup delay can have a different value per patron category, item type or branch. To test: 1) Update database, restart services 2) Set ReservesMaxPickUpDelay syspref (if not already set) 3) Edit your circulation rules and set a value under 'Holds pickup period (day) that is DIFFERENT from ReservesMaxPickUpDelay. Set a few different numbers for different branches as well. 4) Place a hold on a biblio from the staff client. 5) Check in an item from that biblio and confirm the hold as waiting 6) Confirm the expiration date is calculated using the 'Holds pickup period' value instead of the ReservesMaxPickUpDelay syspref 7) Revert the waiting status and delete the hold 8) Re-place the hold on the biblio on the OPAC. Notice that when you change the pick up location, the number of days in the pickup message below the dropdown changes based on the circ rules. 9) Create a holiday with a date that will overlap with the 'Holds pickup period' 10) Check in an item from that biblio and confirm the hold as waiting 11) Confirm the expiration date is calculated using the 'Holds pickup period' value AND considers the special holiday 12) Confirm tests pass t/db_dependent/Holds/WaitingReserves.t 13) Test Talking Tech: 13a) Enable TalkingTechItivaPhoneNotification 13b) Go to Tools -> Notices & slips. Add content to the HOLD phone (itiva) notice. 13c) In your terminal, run perl /path/to/koha/misc/cronjobs/thirdparty/TalkingTech_itiva_outbound.pl -o ~/itiva.tmp -w 0 --type=RESERVE Sponsored-by: Catalyst IT Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32058] New: 'Print > Print X' could use clearer labels
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '22

01 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32058 Bug ID: 32058 Summary: 'Print > Print X' could use clearer labels 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have a 'Print' option in the patron toolbar, it's exposes a number of options all labelled 'Print X'. I would argue as the person has just clicked the 'Print' button to expose the pulldown they already know the options are all 'Print something' so we don't need the 'Print' as part of each label.. I also don't think the existing options are all that clear as to what they're printing... could we rename them more clearly? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3