July 2018 - Koha-bugs - lists.koha-community.org

[Bug 12365] Notes for rules
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '18

26 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12365 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #77147|0 |1 is obsolete| | --- Comment #25 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 77275 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=77275&action=ed… Bug 12365: (follow-up) Adding maxlength attribute and popover Test that you can't add a note of more than 100 characters. Test notes with rules, notes are hidden by 'View note' and the popover correctly displays note. View the note by hovering over the link I've moved the Note column so the popover displays nicely and doesn't cover the buttons. I've also changed the placement so that it doesn't cover information in the row. Update: Test that you can edit the note when clicking 'Edit' and that behaviour is the same for editing all other fields -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20924] New: News content textarea not showing
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '18

26 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20924 Bug ID: 20924 Summary: News content textarea not showing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Created attachment 76013 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76013&action=ed… screenshot showing missing textarea when adding new or editing exiting koha news item, the content textarea box does not show. /cgi-bin/koha/tools/koha-news.pl?op=add_form -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 14413] map internalnotes to MarcFieldsToOrder
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14413 Sandre Cunha <cunha(a)monterey.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cunha(a)monterey.org --- Comment #3 from Sandre Cunha <cunha(a)monterey.org> --- I don't think BZ15503 addresses this enhancement request. One can import order notes from staged vendor files to one of the MarcFieldsToOrder Sort1 or Sort2, but in order to see them in the Order line -Accounting details - internal note [which on can view when receiving the item] it is necessary to copy-and-paste or retype the note. This type of note is useful for acquisitions receiving, to convey information like : item need for program by a certain date; 2 copies to one fund code, 1 to another ; discard old edition when new arrives; and other notes from selector that need to be retained until the item is received. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 12652] Acq: Wrong fund charged for orders created from staged marc records
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12652 Barton Chittenden <barton(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |barton(a)bywatersolutions.com --- Comment #3 from Barton Chittenden <barton(a)bywatersolutions.com> --- I suspect that this is a special case of either Bug 14850: Funds from inactive budgets appear in 'Funds' dropdown on acqui/invoice.pl or Bug 20014: When adding to basket from a staged file item budgets are selected my matching on code, not id -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 21117] New: Highlighting of search terms in the 500 fields
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21117 Bug ID: 21117 Summary: Highlighting of search terms in the 500 fields Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a search term is entered into Koha, it will search the Marc 5xx fields. This will retrieve the results where the search term is found in the 5xx fields. However, the highlighting does not appear when this term is found in the Marc 5xx fields. It would be nice to show the highlighting throughout the Koha record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 13542] Subscripton is only table to store userid instead of borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13542 --- Comment #5 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Jonathan Druart from comment #4) > It is actually worst than that, it is using "loggedinusername" that is a > concatenation of firstname and surname of the logged in librarian. > > This value is never displayed or reused anywhere else. This is wrong, it's the userid! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13542] Subscripton is only table to store userid instead of borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13542 --- Comment #4 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- It is actually worst than that, it is using "loggedinusername" that is a concatenation of firstname and surname of the logged in librarian. This value is never displayed or reused anywhere else. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21061] New: Clean up expired password recovery requests
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21061 Bug ID: 21061 Summary: Clean up expired password recovery requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org >From reading the code it looks like entries to borrower_password_recovery are only cleaned up when an expired verification link is clicked or a password is reset successfully. It would be nice to have an option in cleanup_database to regularly clean up the table by deleting requests expired more than x days. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 14049] Ability to add custom fields to OPAC purchase suggestion form
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14049 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|oleonard(a)myacpl.org |koha-bugs(a)lists.koha-commun | |ity.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14662] Add empty entry to pull down when subfield is mandatory and linked to authorized value
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '18

25 Jul '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14662 --- Comment #5 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Summarizing with a test plan and description of expected behaviour: To test: - Mark collection, itemtype and damaged as mandatory in your MARC framework - Add a new item - Verify that instead of the fields being empty, the first value is selected If there is an itemtype on bilbio level, this itemtype should be selected. Expected behaviour: - All pull downs should offer an empty entry - Empty should be preselected, if there is no - existing value - default in the framework - Only for itemtypes: value in 942$c - If one of those is set, this value should be preselected. -- You are receiving this mail because: You are watching all bug changes.

1 0