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

[Bug 8132] Batch delete tool deletes items with holds on them
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8132 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|batch delete tool deletes |Batch delete tool deletes |items with holds on them |items with holds on them -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 8132] batch delete tool deletes items with holds on them
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8132 --- Comment #23 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Christopher Brannon from comment #22) > (In reply to Jonathan Druart from comment #21) > > Trying to get back to this. > > > > Are we supposed to silently delete an item with an item-level hold that is > > not found (W or T)? > > In my opinion, staff or patron should be notified. At least staff, because > they could make a decision to move the hold to another record, order the > item, or notify the patron that the item is no longer available. I think a notification in the GUI would be good, Maybe at the top, sth like: Following items can't be deleted because they have holds on them? What if it's a record level hold and it's the last item? Maybe we should just check for items in general. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 22846] New: Remove warning in the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22846 Bug ID: 22846 Summary: Remove warning in the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The paragraph in https://koha-community.org/manual/18.11/en/html/systempreferences.html#stat… saying Leaving StaticHoldsQueueWeight empty is contraindicated at this time. Doing so will cause the build_holds_queue script to ignore RandomizeHoldsQueueWeight, causing the script to request hold fulfillment not randomly, but by alphabetical order. is talking about (without mentioning it by number) bug 8562, which was fixed in bug 12803 comment 14. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 4809] Allow to pay lost item replacement fee when changing the lost status
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4809 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Lost & Paid For doesn't |Allow to pay lost item |record payment |replacement fee when | |changing the lost status --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think the comment from Chris on comment#6 is still valid. There is no special behavior tied to any of the lost values - they all do the same thing. If we want a way to immediately mark 'paid' when changing the lost status, this will need more work. Another way might be a pref, where you list the lost values that you want to do that for. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 3642] New information in overdues CSV export
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3642 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|New informations in |New information in overdues |overdues CSV export |CSV export -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23556] New: MARC bibliographic framework test (admin/checkmark.pl) does not consider item-level_itype system preference
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23556 Bug ID: 23556 Summary: MARC bibliographic framework test (admin/checkmark.pl) does not consider item-level_itype system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com MARC bibliographic framework test does not check item-level_itype system preference, so it reports an error on biblioitems.itemtype not mapped and not related to itemtype authorised values if itemtype is at item level -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 22304] New: Bugzilla blocked by UK mobile network EE
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22304 Bug ID: 22304 Summary: Bugzilla blocked by UK mobile network EE Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: Other OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: emma.perks(a)heartofengland.nhs.uk Target Milestone: --- Created attachment 84957 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=84957&action=ed… EE user screenshots - cannot connect to Bugzilla Hello, The bugs.koha-community.org website is blocked by mobile network EE in the UK. When trying to access it using 4G or mobile data provided by EE, the site is blocked due to the security certificate on Bugzilla. One person in the EE community thinks this is caused by EE not doing browser fallback. Several users have tried and all have the same problem independent of hardware. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 23834] New: Add default ESLint configuration
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23834 Bug ID: 23834 Summary: Add default ESLint configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW 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 CC: testopia(a)bugs.koha-community.org Blocks: 23833 Default configuration proposed when the ESLint coding guideline was voted on: { "env": { "browser": true, "jquery": true }, "extends": "eslint:recommended", "rules": { "indent": [ "error", 4 ], "linebreak-style": [ "error", "unix" ], "semi": [ "error", "always" ] } } Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23833 [Bug 23833] [Omnibus] JavaScript should conform to coding guidelines recommended by ESLint -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 23841] New: Add a button to get from an item to it's biblio record
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23841 Bug ID: 23841 Summary: Add a button to get from an item to it's biblio record Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I think it would be handy to have some way how to get from detailed list of items as is this: ../cgi-bin/koha/catalogue/moredetail.pl?biblionumber=61855&itemnumber=66778 to it's biblio "parent": ../cgi-bin/koha/catalogue/detail.pl?biblionumber=61855 TL&DR: Most of the time, librarians arrive to the item page trough it's biblio, but this is not a rule (for example many time we just click on barcode in Circulation module) and simple "back" in browser do not bring person much closer to desired record. I am open to suggestion about form how to do this, but only way I found (for staff without right to edit biblio) till today is to delete parameter "&itemnumber=66778" from URL - and that is not something, I want to teach my staff... Librarians, which are allowed to edit records, can push "Edit" rollout button and then "Edit Record", jump to the Editing, where just "Cancel" button bring them right where they need to be. Simple button with label "Record" (Or "Biblio") in one line with "New", "Edit", "Save", "Add to", "Print" and "Place hold" would be nice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 23762] New: Editing is_html status of email template fails under multi-languages
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '19

03 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23762 Bug ID: 23762 Summary: Editing is_html status of email template fails under multi-languages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: bin.wen(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org letter.tt did not pass the parameter 'lang' of 'is_html' to letter.pl, resulting in the failure to save the 'is_html' value of the corresponding language. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18