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

[Bug 17667] New: Standing orders - cancelling a receipt increase the original quantity
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '20

14 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17667 Bug ID: 17667 Summary: Standing orders - cancelling a receipt increase the original quantity Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org When cancelling a receipt, the quantity of the original order is increased. That does not sound correct. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 15726] New: columns_settings.pl: add option for circulation rules column configuration
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '20

13 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15726 Bug ID: 15726 Summary: columns_settings.pl: add option for circulation rules column configuration Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The circulation rules table is so big, you have to scroll across two full laptop screens. If you know a column is not being used by any location, it would be nice to be able to control the visibility of the columns through the new columns_settings.pl option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 18816] New: Make CataloguingLog work in production by preventing circulation from spamming the log
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '20

13 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18816 Bug ID: 18816 Summary: Make CataloguingLog work in production by preventing circulation from spamming the log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference CataloguingLog is not recommended for use in production. This is do to the fact that every checkin and checkout generates one or more log entires. This seems to be not only bad behavior, but unnecessary and outside the needs of CataloguingLog as we have CirculationLog. -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 17483] New: Forgiving charge should apply to item's last fine.
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '20

11 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17483 Bug ID: 17483 Summary: Forgiving charge should apply to item's last fine. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning an item with a fine, if the Forgive checkbox is clicked, this forgives the first accountline associated to the item/user, not the current/latest as it should. Scenario (Real world): - A patron returns a book late, ensuring a 5$ fine. Does not pay it. - The patron borrows the book again 3 months later. Gets late again, and fined 2$. - Great timing: The library offers amnesty for a week. Bring back your book and we'll forget that they're late. - On checkin, the librarian clicks "Forgive overdue charges" and scan the book. - Koha cancels the 3-months-ago 5$ fine. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 19634] New: Advanced editor - Rancor - error in display of macro editor in firefox
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '20

10 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19634 Bug ID: 19634 Summary: Advanced editor - Rancor - error in display of macro editor in firefox Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 0 - Use firefox 1 - Open the advanced editor 2 - Click 'new macro' 3 - name it 4 - the editor window has only one line This js is a workaround for the moment: $(document).ready(function(){ $("#macro-editor").closest("div.row").css("height","100%"); }); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18231] New: Add the missing id-column to koha.issuingrules-table for DBIC fixtures
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '20

08 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18231 Bug ID: 18231 Summary: Add the missing id-column to koha.issuingrules-table for DBIC fixtures 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Test::DBIx::Class fixtures won't work if the resultset doesn't support last_insert_id. This is only supported with a integer primary key. This patch adds one to issuingrules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 17885] New: Koha::SearchEngine::Elasticsearch-> reset_elasticsearch_mappings throws DBD::mysql Duplicate entry exceptions
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17885 Bug ID: 17885 Summary: Koha::SearchEngine::Elasticsearch->reset_elasticsearch _mappings throws DBD::mysql Duplicate entry exceptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching 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 33

[Bug 16972] New: ./misc/ sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section.
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16972 Bug ID: 16972 Summary: ./misc/sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz As far as I can tell, the following options are mandatory: -a (address) -p (port) -su (sip user) -sp (sip password) -l (sip location/institution) The sip terminator (-t) is not mandatory, but getting it wrong hangs the script without warning. The usage would look like this, more or less: Usage: $0 -a <address> -p <port> -su <sip user> -sp <sip port> -l <location> [--patron <patron barcode>] [--password <patron password>] [-i <item barcode>] [-fa] [-m <message>] [-h] -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18155] New: Add useful classes to the rows of checkouts table
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18155 Bug ID: 18155 Summary: Add useful classes to the rows of checkouts table 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: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries sometimes ask to have different styling in checkouts table according to the item status such as awaiting reservation. Sometimes they need to highlight special document types. So I would propose to add another CSS classes to those already existing, something like: <tr class="odd group-item -group-item-strong.... itype-book hold-awaiting"> The itype class would be concatenated with an item type code. Maybe a class for item's location and overdue item would be useful as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15686] New: Rename "item level holds" circ rule column to "OPAC item level holds"
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '20

01 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15686 Bug ID: 15686 Summary: Rename "item level holds" circ rule column to "OPAC item level holds" Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 5786 moved the OPACItemHolds sys pref setting to the Circulation Rules table. However, the naming of the new circ rules column is quite confusing. It is called "Item level holds" which makes it sound like this setting controls the item level holds placing from anywhere in the system (staff and OPAC sides) Instead, the setting only affects item level hold placing from the OPAC side. Should this column then be renamed to "OPAC item level holds"?, so it's not so confusing? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14