April 2015 - Koha-bugs - lists.koha-community.org

[Bug 4041] Address Format as a I18N/L10N system preference
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '15

29 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4041 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com --- Comment #30 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Guys, could you please change it so a user who is not used to the "us format" or the "german format" can know what the syspref actually does? I'll make it explicit just in case: Please provide a followup (SYSPREF DESCRIPTION ONLY) so it says something like: US format (Street Nº - City - ...) German format (...) Thanks, looking forward to integrate this one ASAP. Also, there's one patch (the last two) that needs to be deprecated. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 12203] New: can't print circ receipts in Chrome
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12203 Bug ID: 12203 Summary: can't print circ receipts in Chrome Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is in Koha 3.14.x and master. If you try to print any of the 3 receipt options on the circ page while in chrome nothing happens. It works a-ok in Firefox -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9117] New: Reports hierarchies management improvements
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9117 Bug ID: 9117 Summary: Reports hierarchies management improvements Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Reports Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com - Filter by groups using tabs - Filter by subgroups using a dropdown list under each tab - Allow to create new group and subgroups when building a new report or editing an existing report (no need to go through admin AV interface) + Possibility to duplicate a report (new link in the table) -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 12217] New: Funds not matching up
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12217 Bug ID: 12217 Summary: Funds not matching up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 28120 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=28120&action=edit Fund lists on main page See attached images. On the acquisitions main page (cgi-bin/koha/acqui/acqui-home.pl) it lists what you have ordered against a fund. When you click the amount (in my images the $238.48) it shows me what makes up that amount (cgi-bin/koha/acqui/ordered.pl?fund=3&fund_code=HDCORTH14) - but it doesn't match. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 12235] New: Logs organized inconsistently
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12235 Bug ID: 12235 Summary: Logs organized inconsistently Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The database structure for the transaction logs doesn't work very well. When you view the "Modification log" for a patron or a bib record, you're viewing the logs for the "object" with that borrowernumber or biblionumber. However, this often has surprising results, especially in the "Catalog" module. For instance, the "Modification log" for bib record #1 will show you the logs for bib record #1...and item record #1. However, if won't show you the logs for item record #2, which is attached to bib record #1. This is a problem. While it might be fair that the "Modification log" for bib record #1 shouldn't have to show the logs for its attached items, it shouldn't show unrelated results for other items. -- A structure more in line with expectation might be something like: -System user (i.e. the librarian) -Biblionumber -Itemnumber (or maybe AttachedNumber so this could be either items or serials) -Info Or at least some other way of differentiating what is in the "object" column. I had to perform 3 different (arguably "expert") queries just to find out that item #2 from bib record #1 was checked in by patron #3. Why? First query: Retrieve bib record...don't find correct item information using bib ionumber object Second query: Retrieve item record using correct itemnumber object... Third query: Search for itemnumber in "info" column, so that it brings up the circulation transaction. -- I'm tempted to write a patch for this, but I wonder about pre-existing logs. Do we try to convert them to match a new schema, or do we ignore them, or do we back them up then wipe the table for fresh logs? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 10680] New: "Modification log" gives wrong data
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10680 Bug ID: 10680 Summary: "Modification log" gives wrong data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When viewing a record, the "Modification log" tab on the left hand side should display the modifications for that biblionumber, but instead it will pull the modifications for the itemnumber instead. That is, if the record you are viewing has a biblionumber of 42, and you follow the "Modification log" link, you will be seeing the modifications for the item whose itemnumber is 42 instead! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 7046] New: subscription renewal period should be a pull down
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7046 Bug #: 7046 Summary: subscription renewal period should be a pull down Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 5938 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5938 renew subscription length When adding a new subscription there is a pull down menu for the subscription length, but when you renew it the length is 3 text boxes which implies that you can fill them all in - or that you have to fill them all in, but I assume you're just supposed to fill in one like you do when you add a subscription. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 6

[Bug 12262] New: Searching patrons by extended attribute should be a search field
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12262 Bug ID: 12262 Summary: Searching patrons by extended attribute should be a search field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for patrons, the search is always also performed on extended attribute, even on when a field is selected (like email, phonenumber ...). And the results which matched only on an extended attribute can not be easily identified. The search on extended attribute should be a field. Or for a start the search on extended attribute could be enabled only for standard field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 12833] New: Patron search no longer searches extended attributes
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12833 Bug ID: 12833 Summary: Patron search no longer searches extended attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 9811 introduced C4::Utils::DataTables::Members::search for searching patrons which does not use C4::Members::Search at all. This is a huge problem that will cause either duplicated code, or missing features! Case in point, the code in C4::Utils::DataTables::Members::search does not take into account searching of extended patron attributes, which introduces a regression. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 12267] New: Allow password option in Patron Attribute non functional
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '15

28 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12267 Bug ID: 12267 Summary: Allow password option in Patron Attribute non functional Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When adding (or editing) a Patron Attribute, the option to "Allow password" can be selected. The purpose here is to allow this attribute/password to be a secondary login for the patron account. [ Allow password: Check to make it possible to associate a password with this attribute ] However, checking the box and then adding a patron with an attribute/password combination does not allow the patron to log on using that attribute password combination. 1. Set up New Patron Attribute, clicking Allow password option. 2. Create a new patron. Enter patron data including the attribute and password value 3. Save patron 4. Using that attribute/password values, attempt to log on to the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4