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

[Bug 30379] New: Create granular permissions for ILL
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30379 Bug ID: 30379 Summary: Create granular permissions for ILL Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: Niamh.WalkerHeadon(a)hse.ie Currently, there is only one permission for ILL on the system. Make these more granular. For example. Allow a staff member to create a request for a patron but don't allow them to manage the request in anyway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 30208] New: Marking an item lost should revert the waiting status of any associated hold
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30208 Bug ID: 30208 Summary: Marking an item lost should revert the waiting status of any associated hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is currently Waiting for pickup for a hold, editing that item to apply a lost status should revert the waiting status of the hold. To recreate: - place an item-level hold - check your item in and confirm the hold - confirm on waitingreserves.pl that Koha shows the item is waiting for pickup - confirm on the request.pl that Koha shows the item is waiting for pickup - edit your item to Lost - confirm the item now shows as both lost and waiting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21236] New: Restore ability to selectively set item to lost without generating fee
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21236 Bug ID: 21236 Summary: Restore ability to selectively set item to lost without generating fee Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Prior to bug 19974 a user could set an item to lost via additem.pl and the item would not be marked as returned and the patron would not be charged the replacement cost. The previous bug sought to standardize behavior between additem.pl and moredetail.pl, making both pages mark lost items and returned and charge the patron. Based on feedback about existing library workflows that relied upon the discrepancy between to two behaviors, the MarkLostItemsasReturned syspref was added to give libraries a choice of when and if an item would be marked as returned when set to lost. However, no such syspref was added to give the option to maintain the inconsistent legacy behavior in charging replacement costs when items are lost. This breaks existing workflows for libraries using lost status to handle Claims Returned items where the intent is to mark an item as lost but not charge the patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 24319] New: When RenewSerialAddsSuggestion is used, use existing record when ordering from suggestion
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24319 Bug ID: 24319 Summary: When RenewSerialAddsSuggestion is used, use existing record when ordering from suggestion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 When renewing a serial subscription a suggestion in the acquisition module can be automatically created using the RenewSerialAddsSuggestion system preference. While the biblionumber can be stored, this will create a new record on 'ordering from a suggestoin' later on. It would be much better, if we attached the order to the existing record instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24318] New: When RenewSerialAddsSuggestion is used, treat suggestion as "order from subscription"
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24318 Bug ID: 24318 Summary: When RenewSerialAddsSuggestion is used, treat suggestion as "order from subscription" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 At the moment, you can add add a suggestion on renewing a subscription, using the RenewSerialAddsSuggestion system preference. The suggestion is disconnected from the subscription, as we don't store the subscription id. When the suggestion is accepted, a new record is created and there is no connection to the existing one. We should store the subscriptionid and treat the order as a 'order from subscription', which will give it all the features available for subscription ordering at the moment and form a good connection between the serials and acq modules. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 24092] New: Change Koha::Item to use Items::LastPatrons instead of ItemLastBorrower resultset
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24092 Bug ID: 24092 Summary: Change Koha::Item to use Items::LastPatrons instead of ItemLastBorrower resultset Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Koha::Item uses my $items_last_returned_by_rs = Koha::Database->new()->schema()->resultset('ItemsLastBorrower'); to retrieve item's last borrower. It should use Items::LastPatrons class introduced in bug 23260 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26994] New: Display list of names in alphabetical order when using the Suggestion Information filter in Suggestions Management
by bugzilla-daemon＠bugs.koha-community.org 28 Nov '23

28 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26994 Bug ID: 26994 Summary: Display list of names in alphabetical order when using the Suggestion Information filter in Suggestions Management Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org In Suggestions Management when filtering searches using the Suggestion Information filter and then using the 'Suggested by', 'Managed by' or 'Accepted by' dropdowns it would be helpful if the list of names was displayed in alphabetical order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 23789] New: fr-CA translation of AUTO_RENEWALS notice
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '23

24 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23789 Bug ID: 23789 Summary: fr-CA translation of AUTO_RENEWALS notice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 20595] New: EDI: Add support for LRP (Library Rotation Plan) for Koha with Stock Rotation enabled
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '23

24 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20595 Bug ID: 20595 Summary: EDI: Add support for LRP (Library Rotation Plan) for Koha with Stock Rotation enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: alex.sassmannshausen(a)gmail.com, andrew.isherwood(a)ptfs-europe.com, fiona.borthwick(a)ptfs-europe.com, gmcharlt(a)gmail.com, jonathan.druart(a)bugs.koha-community.org, jonathan.field(a)ptfs-europe.com, josef.moravec(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle.m.hall(a)gmail.com, kyle(a)bywatersolutions.com, lisetteslatah(a)gmail.com, liz(a)catalyst.net.nz, sally.healey(a)cheshiresharedservices.gov.uk, tomascohen(a)gmail.com Depends on: 11897, 14187, 18137 This submission will add the support for the Edifact LRP field in Koha, using the field to automatically add ordered items to stock rotation plans. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 [Bug 11897] Stock Rotation for Koha https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14187 [Bug 14187] branchtransfer needs a primary key (id) for DBIx and common sense. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18137 [Bug 18137] Migrate from Mojolicious::Plugin::Swagger2 to Mojolicious::Plugin::OpenAPI -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 20670] New: Add markup and standard classes for sidebars and main content areas
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20670 Bug ID: 20670 Summary: Add markup and standard classes for sidebars and main content areas Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED 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 Blocks: 14546 As we move away from YUI grids, it would be helpful if we could consistently add some classes to the primary sections of the page. That would allow us to style elements differently based on their container's class. I've already begun adding a "main" class to the <div> which is the primary "container" for the Bootstrap grid. It typically looks like this: <div class="main container-fluid"> <div class="row"> <div class="col-sm-5 col-md-4"> I would like to add an additional container that wraps the primary content region for the page. This container should have no style attached to it (as it might interfere with grid layout), but can serve as a context for styles within it. ----------------------------------------------- * .main * * ------------------------------------------- * * * * .main-content * * * * * * * * * .sidebar * -------------------------- * * * * * * * * * * * * * .row * * * * * * * .col-* * * * * * * * ...etc. * * * * * * -------------------------- * * * * * * * * ------------------------------------------- * * * ----------------------------------------------- The use I have right away is to style forms differently based on whether they are in the sidebar or the main-content area. Right now we have some CSS which depends on YUI grid classes, and we need to replace that which isn't dependent on the grid system we choose. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive -- You are receiving this mail because: You are watching all bug changes.

1 7