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

[Bug 21346] New: Remove return2 div from returns.tt now that modal interface exists
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '20

23 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21346 Bug ID: 21346 Summary: Remove return2 div from returns.tt now that modal interface exists 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Someone added a new modal for holds/transfers in return.tt (yay!). They left the old dialog in the background, and if you ignore the modal, it remains. To replicate: 1) Place a hold on an item from Branch A to be delivered to Branch B. 2) Checkin in the item at Branch A and confirm the hold to transfer. 3) Be human and make a mistake. Login as Branch C and check the item in. 4) Note the great modal to redirect the hold. Note that the old dialog is behind it! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 104

[Bug 21049] New: Rancor 007 field does not retain value
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '20

22 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21049 Bug ID: 21049 Summary: Rancor 007 field does not retain value Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using Rancor, 007 field editor, you select the material type, and as soon as the record is saved, it reverts to the first material type in the list. The information is saved correctly, but every time the record gets edited the correct material type has to be selected again or else it is saved as the material type listed first in the dropdown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 22002] New: Each message_transport_type in the letters table is showing as a separate notice in Tools > Notices and slips
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '20

22 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22002 Bug ID: 22002 Summary: Each message_transport_type in the letters table is showing as a separate notice in Tools > Notices and slips Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 83225 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=83225&action=ed… Screenshot showing multiple rows for PREDUE notice Each message type (email, phone, print, sms) has a separate row on Home › Tools › Notices & slips. To replicate: 1) Go to Home › Tools › Notices & slips 2) Choose a letter to edit, e.g. PREDUE. Note that there is only a single row. 3) Click the edit button on the notice. 4) Expand the 'Print' section. Put text into the Message subject and Message body text areas. 5) Click save, this will take you back to the 'Notices & slips' page. 6) An extra row shows for this notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 16421] New: Move hold edit actions into dropdown menu
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '20

22 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16421 Bug ID: 16421 Summary: Move hold edit actions into dropdown menu Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/reserve/request.pl OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 51111 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51111&action=ed… Screenshot showing proposed interface change I propose that we re-work the way existing holds are displayed in the staff client so that many of the actions associated with a hold are moved into a dropdown menu. I would also add some additional information about the status of a hold into the "details" column. This change would accomplish a few things: - Make the display more compact - Make clearer some information which may not be clear. For instance, that a hold is suspended until a particular date, or that a hold is set to lowest priority. - Make clearer the meaning of the hold priority icons. Using text labels with icons, the meaning of each is explicit. Unfortunately Font Awesome doesn't have the equivalent of the "move to top" or "move to bottom" icon, so I've tried to fake it with a border. It's not perfect buy may be passable. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 22658] New: aqbasket.authorisedby is missing a foreign key constraint
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '20

21 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22658 Bug ID: 22658 Summary: aqbasket.authorisedby is missing a foreign key constraint 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The aqbasket table optionally references a number of tables, but the foreign key fields are unconstrained. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 21206] New: C4::Items - Remove GetItem
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '20

21 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21206 Bug ID: 21206 Summary: C4::Items - Remove GetItem Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Let's use Koha::Items! -- You are receiving this mail because: You are watching all bug changes.

1 67

[Bug 19417] New: Improve display of errors from background job during stage for import
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '20

21 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19417 Bug ID: 19417 Summary: Improve display of errors from background job during stage for import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When importing records, if there is an error in the staging we display: Failed to submit form: error This is not helpful, we should instead display the error textReponse field -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 18874] New: Add unique constraint to repeatable_holidays and special_holidays
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '20

20 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18874 Bug ID: 18874 Summary: Add unique constraint to repeatable_holidays and special_holidays Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The calendar doesn't check if holidays already exist before copying/inserting holidays -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 22566] New: Stock rotation cronjob reporting has issues
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '20

17 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22566 Bug ID: 22566 Summary: Stock rotation cronjob reporting has issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- Trying to test this today we found that some of the reporting features of the cronjob seem to be problematic: To recreate: 1 - Create some rotas 2 - Add some items 3 - run cronjob with -x 4 - in sql UPDATE branchtransfers SET datearrived=DATE_SUB(CURDATE(), INTERVAL 1 DAY) WHERE comments like '%rota%' 5 - run the cornjob without -x: perl misc/cronjobs/stockrotation.pl -r full 6 - get an error about undefined emails 7 - run it for branch emails perl misc/cronjobs/stockrotation.pl -r email 8 - get an error about odd numebr of elements in hash -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 23089] New: Elasticsearch - cannot sort on non-text fields
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '20

16 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23089 Bug ID: 23089 Summary: Elasticsearch - cannot sort on non-text fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- issues is defined as an sum field, this is interpreted to ES as integer, however, the issues__sort field is stored as keyword. Attempting to order search results by 'popularity' fails from ES - because we can't use text fields, we have to use a 'keyword' field. In our biblio search indexes this is fine because our __sort fields all get a phrase keyword field We onyl set field__sort.phrase for text fields though, so issues__sort doesn't use the phrase field, even though it exists Adding a test to try to ilustrate what I am saying here To recreate: 1 - Enable and index ES 2 - Search on staff client or OPAC 3 - Attempt to sort by popularity 4 - It fails, check the error logs to see why -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41