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

[Bug 18786] New: Add ability to create custom payment types
by bugzilla-daemon＠bugs.koha-community.org 10 May '19

10 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18786 Bug ID: 18786 Summary: Add ability to create custom payment types 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 14826 Some libraries would like to be able to specify more specific payment types such as cash, check, credit card, or even canned food ( for food drives ). This feature will allow a library to specify payment types as authorised values of the type PAYMENT_TYPE. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14826 [Bug 14826] Resurrect account offsets table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 22453] New: TestBuilder should generate now() using the current timezone
by bugzilla-daemon＠bugs.koha-community.org 08 May '19

08 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22453 Bug ID: 22453 Summary: TestBuilder should generate now() using the current timezone Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I have no idea why this only appears today but TestBuilder generates dates using DateTime->now, which does not take into account the timezone. It has been highlights by a failing test today on U18. Why today whereas this patch was pushed few weeks ago? Why U18 and not D9? The output of the test is: koha_1 | # Failed test 'With BorrowerLogs and TrackLastPatronActivity we should not spam the logs' koha_1 | # at t/db_dependent/Koha/Patrons.t line 1421. koha_1 | # got: '2' koha_1 | # expected: '1' koha_1 | # Looks like you failed 1 test of 4. koha_1 | koha_1 | # Failed test 'BorrowersLog tests' koha_1 | # at t/db_dependent/Koha/Patrons.t line 1422. koha_1 | # Looks like you failed 1 test of 33. koha_1 | [19:51:44] t/db_dependent/Koha/Patrons.t Actually there are 2 logs, one for the cardnumber that is expected, and on for updated_on: "updated_on" : { "after" : "2019-03-04 21:10:00", "before" : "2019-03-04 18:10:00" } Apart from the fact that we may want to remove this updated_on field from MODIFY, the before/after dates differ from 3 hours. Here it's currently 18:10 and in UTC-3 To prevent such behaviors in tests (create stuffs in the future...), we should use our Koha::DateUtils::dt_from_string method that takes care of the timezone used in other places of Koha. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 22424] New: Add search by all lost statuses to item search
by bugzilla-daemon＠bugs.koha-community.org 08 May '19

08 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22424 Bug ID: 22424 Summary: Add search by all lost statuses to item search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently item search has "lost" as a yes or no field. Lost should be searchable just like "not for loan," listing all the authorized values configured. Search results should include a column for "Lost." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 22537] New: Suspend all hold button appears even if the hold can no longer be suspended.
by bugzilla-daemon＠bugs.koha-community.org 08 May '19

08 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22537 Bug ID: 22537 Summary: Suspend all hold button appears even if the hold can no longer be suspended. 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 86742 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=86742&action=ed… suspend_hold Hi, I understand that a hold can not be suspended when it is awaiting for pickup. This is why the Suspend column is empty in the opac user's account. However, "Suspend all holds" button still appears and causes misunderstanding. Nothing happens when you click on the button but the user thinks that his hold has been suspended. See image attached. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 21415] New: Set maxreserves by borrower category
by bugzilla-daemon＠bugs.koha-community.org 08 May '19

08 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21415 Bug ID: 21415 Summary: Set maxreserves by borrower category Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently the system preference MaxReserves sets an overall limit for reserves across all item types for all borrower categories. It would be helpful to allow this limit to differ based on category code. Be aware that there is already a bug asking for a the ability to differ MaxReserves by branch (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7030) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 17750] New: Drop down list in the add biblio page is not responding when the field is repeated
by bugzilla-daemon＠bugs.koha-community.org 07 May '19

07 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17750 Bug ID: 17750 Summary: Drop down list in the add biblio page is not responding when the field is repeated Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: jawad_makki(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 58081 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58081&action=ed… Drop-Down list is not responding when it is duplicated After upgrading KOHA from version 3.22 to version 16.11, the drop down list in the add biblio page is not responding when a field is duplicated. By the drop down list, I mean the authorized values linked to a subfield in MARC frameworks. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 19181] New: Intranet and OPAC authentication selenium test
by bugzilla-daemon＠bugs.koha-community.org 06 May '19

06 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19181 Bug ID: 19181 Summary: Intranet and OPAC authentication selenium test Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org This Selenium tests is to test authentication of a patron to the OPAC and intranet. It follows a similar workflow to the basic_workflow.t text by initially creating a patron category and patron user. Then the superlibrarian user used to create these logs out and the created patron logs into the staff intranet and OPAC -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 21124] New: Non-Public note does not appear if added to item in MARC field
by bugzilla-daemon＠bugs.koha-community.org 06 May '19

06 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21124 Bug ID: 21124 Summary: Non-Public note does not appear if added to item in MARC field Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: danield(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 77294 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=77294&action=ed… Non-public note field when editing an item Adding a non-public note when in the item detail area (moredetail.pl) works as expected ie. it's visible in the normal title view, when returning/issuing, etc. When adding a non-public note in the edit item screen (additem.pl?op=edititem), the note will save, but will not appear in the areas it is supposed to be visible. Similarly this will occur if you try to batch modify a group of items adding a non-public note. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 18639] New: Separate replacement cost and retail price fields in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 06 May '19

06 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18639 Bug ID: 18639 Summary: Separate replacement cost and retail price fields in acquisitions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Work to be done: 1 - Add a field 'replacementprice' to the aqorders table 2 - Display this field as 'Replacement price' when ordering 3 - Rename current 'Replacement price' field for orders to 'Retail price' 3a - 'Retail price' field will only be editable during initial ordering 3b - If 'Retail price' field is update, dependent fields will also be updated (currently they are only updated on change of 'lsit price') 4 - Allow for replacementprice to be populated via ItemFieldsToOrder preferences 5 - Adjust EDI scripts to allow for use of 'replacementprice' field 6 - Pass 'replacementprice' in aqorders through as 'items.replacementprice' when creating items 7 - aqorders.replacementprice should be editable throughout entire acquisitions workflow -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 17707] New: Check out and due date are same
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17707 Bug ID: 17707 Summary: Check out and due date are same Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 57860 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57860&action=ed… Circulation module screenshot My Koha version 16.05.5 Check out and due dates are same. Please see the attached screenshot. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5