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

[Bug 17214] New: Add item in LIST by Record number
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17214 Bug ID: 17214 Summary: Add item in LIST by Record number Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: mishravk79(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Once the LIST is created in Koha you can add item in that by barcode but is there any option to add item by record number because if there is no barcode assigned to the item how it can be added to the list? For example in case of remotely available resources like e-book/e-journals where library may enter only bibliographic details. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 17334] New: members-update.pl should show timestamp
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17334 Bug ID: 17334 Summary: members-update.pl should show timestamp 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the management of patron updates, it seems logical that the requests should show the timestamp of when the request was placed. Yes, you can look this up in a report, but this should be a basic feature of managing requests. Ideally, it should show on the same line as the patron name. Probably something like "Requested: 2016-09-05" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 17477] New: Duplicating a subfield yields an empty subfield tag
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17477 Bug ID: 17477 Summary: Duplicating a subfield yields an empty subfield tag Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 17152 made the subfield cloning function delete the contents of the cloned subfield. But it makes the subfield tag empty too, and this is causing troubles for people re-opening the records for edition. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 19165] New: When adding from a staged file order discounts are not passed into C4:: Acquisitions::populate_order_with_prices
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19165 Bug ID: 19165 Summary: When adding from a staged file order discounts are not passed into C4::Acquisitions::populate_order_with_prices Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: christophe.croullebois(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Discounts are not stored in $orderinfo before passing to populate prices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 19276] New: CanBookBeIssued: unsuccessfully refers to borrower category_type X
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19276 Bug ID: 19276 Summary: CanBookBeIssued: unsuccessfully refers to borrower category_type X Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This code seems to be unused now: if ( $borrower->{'category_type'} eq 'X' && ( $item->{barcode} )) { # stats only borrower -- add entry to statistics table, and return issuingimpossible{STATS} = 1 . &UpdateStats({ ... Why? The key category_type does not exist. Or perhaps does no longer exist. Perhaps it has been refactored to a Koha object hash or something ? The check itself refers to a column in the categories table that formerly got included in the borrower hash. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 18282] New: OpenAPI operationId must be unique
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18282 Bug ID: 18282 Summary: OpenAPI operationId must be unique Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org operationId has the following documentation: "Unique string used to identify the operation. The id MUST be unique among all operations described in the API." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 18290] New: Fix t/db_dependent/Koha/Object.t, Mojo::JSON:: Bool is a JSON::PP::Boolean :)
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18290 Bug ID: 18290 Summary: Fix t/db_dependent/Koha/Object.t, Mojo::JSON::Bool is a JSON::PP::Boolean :) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 19119] New: Remove t/db_dependent/api/v1/swagger/definitions.t
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19119 Bug ID: 19119 Summary: Remove t/db_dependent/api/v1/swagger/definitions.t 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org While it might have seemed a good idea to have such a test, I find it useless as-is, because there's no obvious reason why we would expose our model on the API spec while it is just user-facing and not a technical explanation on how we do things inside our codebase. A good example of this could be bug 18120, in which it is obvious that some attribute names are misleading or the attributes themselves need to be stripped out of the object for exposing on the API. There can be ways of doing this two operations (i.e. removing/adding attributes, and renaming) without handling it on the controller as those patches do. But in any case, there's no need for definitions.t. We could have a gentle 'warning' in the QA tools in case of a column being added to the DB structure and not to the corresponding endpoint, but it has to be a soft requirement IMO. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 18508] New: Fix t/db_dependent/api/v1/swagger/definitions.t ( follow-up of 18137)
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '17

27 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18508 Bug ID: 18508 Summary: Fix t/db_dependent/api/v1/swagger/definitions.t (follow-up of 18137) 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: lari.taskula(a)jns.fi QA Contact: gmcharlt(a)gmail.com t/db_dependent/api/v1/swagger/definitions.t .. Can't locate object method "cache_dir" via package "Swagger2::SchemaValidator" at /usr/share/perl5/Swagger2.pm line 42. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 17077] New: Write off all does not let you write a description
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '17

26 Oct '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17077 Bug ID: 17077 Summary: Write off all does not let you write a description 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: larit(a)student.uef.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When writing off all patron's fines, librarian should be taken to a page where they can write a description for the write-off. It works for individual write-offs, but not for "Write off all". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2