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

[Bug 16167] New: Authorised value images may be removed
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '19

29 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16167 Bug ID: 16167 Summary: Authorised value images may be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16041 The feature to attach an image to an authorised value does not seem to work perfectly and it's possible that nobody uses it. I'd suggest to discuss about that removal on this bug report. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16041 [Bug 16041] StaffAuthorisedValueImages & AuthorisedValueImages preferences - impact on search performace -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 17101] New: Confirm a question before check in
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '19

26 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17101 Bug ID: 17101 Summary: Confirm a question before check in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: T.Reimann95(a)gmx.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Here should be a new option for checkin message by itemtypes implemented. This new option required a confirmation from the user (over a question which is written there) bevor the item is checked in. The only possible answer for the question are yes or no. By yes the item is checked in, by no it's not checked in. To give an example what is meant here: If you create the item type audiobook, you then can add the Check in Message : "Does envelope and content match?" and for the check in message type: question. So if now a item with the item type audiobook is checked in, the user is ask : "Does envelope and content match?" and got the answer possibiltys yes and no. At this moment he can't read a new barcode, so he must answer the question. If he answer yes the item is check in, if he answer no the item is not check in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 17899] New: Show only mine does not work in newordersuggestion.pl
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '19

24 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17899 Bug ID: 17899 Summary: Show only mine does not work in newordersuggestion.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 12775 added a link "Show only mine" in newordersuggestion.pl. This does not work, no results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 18163] New: Elasticsearch itemtype indexing correctly for unimarc
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '19

22 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18163 Bug ID: 18163 Summary: Elasticsearch itemtype indexing correctly for unimarc Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org After installing and indexing Elasticsearch, a search for itemtype is not working correctly. The reason for this I think is that Marc21 uses the index itype whereas Unimarc uses the index itemtype. The index mapped in mappings.yml is itype, and a search for item type in unimarc will search on itemtype index, which has nothing mapped to. Furthermore, trying to change the index from itype to itemtype in the mappings panel for elasticsearch will trigger the following error: Can't call method "label" on an undefined value at /usr/share/koha/intranet/cgi-bin/admin/searchengine/elasticsearch/mappings.pl line 69 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 17535] New: Regression: Search for reports by keyword
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '19

09 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17535 Bug ID: 17535 Summary: Regression: Search for reports by keyword Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Reports Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14435 Introduced by bug 14435 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14435 [Bug 14435] Recover feature to store and access results of a report -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 17501] New: Koha Objects for uploaded files
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '19

05 Apr '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17501 Bug ID: 17501 Summary: Koha Objects for uploaded files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Some code in Koha::Upload can be moved to Koha::Object(s). Provides groundwork for further work. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 18060] New: Add onboarding functionality to guide users through setting up labels for the first time
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '19

21 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18060 Bug ID: 18060 Summary: Add onboarding functionality to guide users through setting up labels for the first time Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To help make the process of creating a label for the first time easier this bug report requires the implementation of onboarding tool in the labels area of the staff client to be run the first time the user wants to create a label. The features of the onboarding tool includes tooltips and modal boxes to be displayed to the user to clarify the process to make a label. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 15911] New: Use noEnterSubmit CSS class instead of prevent_submit.js
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '19

19 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15911 Bug ID: 15911 Summary: Use noEnterSubmit CSS class instead of prevent_submit.js 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: jonathan.druart(a)bugs.koha-community.org The JavaScript file prevent_submit.js seems to be doing the same work that the .noEnterSubmit CSS class does via staff-global.js. If so, the extra file should be removed and the templates modified to work with staff-global.js. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16817] New: Apply hold fee on collection not application
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '19

18 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16817 Bug ID: 16817 Summary: Apply hold fee on collection not application Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Patrons are charged for holds as soon as they request an item. We would like patrons to be charged once the item is ready for collection instead. Could this be a system preference? Could the hold fee be applied to the patron's account once the item has been confirmed as ready for collection? Could the generation of the charge be tied to the generation of the Hold Available for Pickup notice? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 15734] New: Audio Alerts issues in master
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '19

16 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15734 Bug ID: 15734 Summary: Audio Alerts issues in master Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org >From Nick: In master there is a JSON error thrown when AudioAlerts are enabled. When checking in I get: SyntaxError: JSON.parse: expected property name or '}' at line 1 column 3 of the JSON data This does not happen in 3.22 -- You are receiving this mail because: You are watching all bug changes.

1 50