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

[Bug 19795] New: Allow files to be uploaded and stored in object storage ( Swift and S3)
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '23

13 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19795 Bug ID: 19795 Summary: Allow files to be uploaded and stored in object storage (Swift and S3) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Currently if we enable uploading and attaching files to a biblio, we only have the option to store the locally on the file system. More and more Koha are being hosted in the "cloud" we should allow people to use the object storage offerings to store their uploaded files. This bug will add support for Openstack Swift, and Amazon S3 only, and only for files attached to biblios. However the code should be able to be used for book covers etc in the future if someone wants to add that feature -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 18974] New: Adding further selenium tests
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '23

11 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18974 Bug ID: 18974 Summary: Adding further selenium tests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org The patches attached to this bug report will be building on the work completed in bug 13691, and 18804 by adding more selenium tests to the t/db_dependent/selenium directory. These selenium tests will test the following: * Authenticating a patron (not default user) into both OPAC and intranet * Searching for item in OPAC and intranet * Go through web installer and onboarding tool * Submitting a purchase suggestion in OPAC * Creating a currency, budget and fund -- You are receiving this mail because: You are watching all bug changes.

1 51

[Bug 17735] New: Merge boraccount and pay pages into one
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17735 Bug ID: 17735 Summary: Merge boraccount and pay pages into one 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We don't really need to have this agenda on two pages - using the one pages would be simpler and makes the workflow more straightforward -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 16959] New: E-mail alerts for saved searches
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16959 Bug ID: 16959 Summary: E-mail alerts for saved searches 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 It would be nice if Koha allowed to send e-mails to patrons when a new record is created for a saved search. Examples: - New records are added within a specific call number range - New records where the title contains certain words It should be possible to set this up individually per patron. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 20755] New: Allow separate email configuration for acq emails
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20755 Bug ID: 20755 Summary: Allow separate email configuration for acq emails 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 the emails in acuisistion (claims and orders) are sent with the email address of the librarian that triggers the sending. This is not practical in all cases for several reasons and it would be nicer if a general acquisition team email could be used. The development should allow to configure the email on library level with a from, replyto and returnpath address similar to the branchemail and it's options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 17499] New: Koha objects for messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17499 Bug ID: 17499 Summary: Koha objects for messaging preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Create Koha objects for messaging preferences. We need to create REST API endpoint for managing patron messaging preferences and this is the first step. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 241

[Bug 21384] New: ILL requests table - allow patron sorting by last name
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21384 Bug ID: 21384 Summary: ILL requests table - allow patron sorting by last name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Currently only sorting by first name is possible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

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