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

[Bug 35326] New: Staff confirmation on shared accounts
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35326 Bug ID: 35326 Summary: Staff confirmation on shared accounts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries use a single account for multiple staff to use, like at a front desk. It would be great if we could mark such accounts, and when certain actions are recorded, Koha would prompt for a staff name. For example, any time a patron record is created or modified, item or bib records created/modified, holds modified, etc. It doesn't have to be everything a staff member does. But it should be some key things. Maybe we could have a preference for this. Ideally it would much simpler if libraries didn't use shared accounts, but since all libraries are different, and this can be a common practice, some of us would might like there to be a way to better track who is doing what. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 26554] New: allow news tag in all slips
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26554 Bug ID: 26554 Summary: allow news tag in all slips Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org Hi all & thanks, as far I understand it, the <news> tag works only in ISSUESLIP. Is there a good reason for this? For us it would be usefull if we could include the news section in all communications/slips cheers & thx Mark -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 12044] Checkout should be clearly disallowed before inputting item barcode if a patron's fines will block the transaction
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12044 Cab Vinton <bibliwho(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bibliwho(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35324] New: Display for items not correct on receive for subscription orders
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35324 Bug ID: 35324 Summary: Display for items not correct on receive for subscription orders 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 8179 There are some cases, where we show the header of the item table to the left on the receive form, when there are no items. We should not be doing that. It seems to always happen, when we have a subscription order. It could also be that this points to missing functionality, as for subscriptions, we should have a separate table with additional information. The cases where something is not quite right are marked with a *: Items in cataloging * ordered 1, receive 1 * ordered 5, receive 2 * standing order, received on multiple invoices * subscription* * subscription + standing order* Items on receive * ordered 1, receive 1 * ordered 5, receive 2 * standing order, received on multiple invoices * subscription* * subscription + standing order* Items on order * ordered 1, receive 1 * ordered 5, receive 2 * standing order, received on multiple invoices * subscription (no items, because it's a subscription order)* * subscription + standing order (no items, because it's a subscription order)* Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 [Bug 8179] Receiving multiple order lines at once -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 8179] Receiving multiple order lines at once
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35324 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35324 [Bug 35324] Display for items not correct on receive for subscription orders -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35186] New: Remove html tags from sample notices
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35186 Bug ID: 35186 Summary: Remove html tags from sample notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 34704 HTML notices don't require that we explicitly add <html> tags. We have 2 notices where these are included in the sample notices and should be removed: PASSWORD_RESET STAFF_PASSWORD_RESET Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34704 [Bug 34704] Print templates are formatted incorrectly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34424] New: Update release team on about page for new QA team member
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34424 Bug ID: 34424 Summary: Update release team on about page for new QA team member Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: emily.lamancusa(a)montgomerycountymd.gov, martin.renvoize(a)ptfs-europe.com We've added Emily Lamancusa as new QA team member, the about page should be updated accordingly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 31393] New: shibboleth broken since migration from XML::Simple
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31393 Bug ID: 31393 Summary: shibboleth broken since migration from XML::Simple Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi, shibboleth can use content in its koha-conf.xml mapping but content key is optimized out if it's the only key before #28278 : koha-conf <branchcode content="foo"/> perl: 'branchcode' => { 'content' => 'foo' }, Now <branchcode content="foo"/> perl: 'branchcode' => 'foo', It's faster but it breaks C4/Auth_with_shibboleth.pm while ( my ( $key, $entry ) = each %{$config->{'mapping'}} ) { if ( any { /(^psgi\.|^plack\.)/i } keys %ENV ) { $borrower{$key} = ( $entry->{'is'} && $ENV{"HTTP_" . uc($entry->{'is'}) } ) || $entry->{'content'} || ''; } else { $borrower{$key} = ( $entry->{'is'} && $ENV{ $entry->{'is'} } ) || $entry->{'content'} || ''; } } -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 29811] New: misc/export_records.pl add possibility to export with timestamp option on authority record type
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29811 Bug ID: 29811 Summary: misc/export_records.pl add possibility to export with timestamp option on authority record type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org misc/export_records.pl got many options, include bibs export based on a certain timestamp but it doesn't exist for authority record type. It can be interresting to add this option for authority according to the timestamp field (modification_time) already present in the database. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 22712] New: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '23

13 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22712 Bug ID: 22712 Summary: Funds from inactive budgets appear on Item details if using MarcItemFieldstoOrder Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 88047 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=88047&action=ed… drop down Bug 14850 has been fixed and patched for 18.11. This removes the ability to see inactive funds when allocating orders to these funds from an inactive budget. However, if a library is using the system preference MarcItemFieldstoOrder, all the funds will appear in the drop-down menu for that item record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22