March 2016 - Koha-bugs - lists.koha-community.org

[Bug 15732] New: Remove accountno column from accountlines
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '19

08 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15732 Bug ID: 15732 Summary: Remove accountno column from accountlines 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 How that we have accountlines_id, accountno is superfluous. We should remove it. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16111] New: RSS feed for OPAC search results has wrong content type
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '19

10 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16111 Bug ID: 16111 Summary: RSS feed for OPAC search results has wrong content type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As a result of (ancient) commit f6e1214c, OPAC search result RSS feeds come over with the content type text/html. It should be at least text/xml, and with the demise of Internet Explorer 6, arguably application/rss+xml. The cause: prior to that commit, setting the CGI parameter format to rss2 resulted in passing "rss" as the content type parameter to output_with_http_headers; after that commit, rss2 was no longer properly recognized when setting that parameter. The main user-visible consequence is that clicking on the RSS link in Chrome (when no feed-reader plugin is installed) renders the feed as HTML rather than XML. -- You are receiving this mail because: You are watching all bug changes.

1 115

[Bug 15679] New: Reset item level hold back to record level hold without deleting and readding the hold
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '19

26 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 Bug ID: 15679 Summary: Reset item level hold back to record level hold without deleting and readding the hold Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Right now, if a hold is tied to a specific item (for any number of reasons), and it needs to be set back to a title level hold, you have to delete and readd the hold. This is cumbersome enough, but it's even more cumbersome when a record has multiple holds (especially 20+), and the hold has to be replaced and manually back in its original priority order. It would be nice if Koha could allow you to reset a hold back to record level after it's been placed, for all cases, including when it's in transit for a patron. Situations arise where an item arrives damaged or is lost in transit and a new item is needed to fulfill the hold. There should probably be a permission to control access to this proposed functionality, like the existing modify_holds_priority permission. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 15814] New: Templates for MARC modification: Edit action does not work.
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '19

20 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15814 Bug ID: 15814 Summary: Templates for MARC modification: Edit action does not work. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org There is an edit button in the tool for MARC template modification for every action of a template. Expected: click edit for an action, get a form populated with the related values. Actual result: page is scrolled to "Add new action", fields are empty. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 15699] New: Course reserves instructors should be in form "Surname, Firstname" for sorting purposes
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '19

25 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15699 Bug ID: 15699 Summary: Course reserves instructors should be in form "Surname, Firstname" for sorting purposes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 15737] New: Patron userid lost during test for duplicate users
by bugzilla-daemon＠bugs.koha-community.org 30 May '19

30 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15737 Bug ID: 15737 Summary: Patron userid lost during test for duplicate users Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you create a new patron record and manually assign a unique cardnumber (userid in the borrowers table) and Koha identifies a possible duplicate record, clicking OK to create the user as a new user causes the manually-assigned userid to be replaced with the user's firstname.lastname. The manually entered userid should be remembered (as long as it is genuinely unique). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[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 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 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

[Bug 16113] New: Specify due date for batch check out
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '19

06 Mar '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16113 Bug ID: 16113 Summary: Specify due date for batch check out 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, Currently , we can not manually select a due date in the batch check out tool. This could be a system preference like specifyDueDate or SpecifyReturnDate. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2