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

[Bug 27791] New: Add 'fixed price' and 'variable price' options to debit types
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27791 Bug ID: 27791 Summary: Add 'fixed price' and 'variable price' options to debit types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, in the point of sale system, we allow inline editing for both "Price" and "Quantity" of items being sold. This means that, even though a default price can be added to an item, staff can always override that price at point of sale by editing it. Some libraries would prefer for this to be an explicit option so for certain items the price is fixed, whilst for others the price may be variable and require staff input to get right. Use case examples: * Pencil - You may have a stock of pencils to sell, a pencil has a fixed price of £1 and staff should not be able to charge more or less.. 'Fixed price' * Book - You may sell off your old stock.. rather than entering a debit type for each and every book you sell you want to have one debit type and to enter a price at the point of sale as advertised on the book itself.. 'Variable price' We could even adapt the workflow this way to actually request the price in a modal that appears between the 'Add' button being pressed and the item appearing in the 'This sale' table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 27780] New: Add ability to set a customised default sort order for sale items
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27780 Bug ID: 27780 Summary: Add ability to set a customised default sort order for sale items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The 'Items for purchase' table on the point of sale page can be sorted by code or description. However, it would be beneficial to have 'popular' items appear at the top to prevent the requirement for searching for these items. We have a few options: * We could attempt to calculate this popularity dynamically. * We could add a user-definable sort field in debit types. * We could add a 'popular' flag to the debit types and then sort on 'popular + code/description'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 23046] New: Add tax handling to accounts
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '25

25 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23046 Bug ID: 23046 Summary: Add tax handling to accounts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should have the ability to assign tax rates to the various charges a patron can incur. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 24599] New: Add endpoints for bulk processing of holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24599 Bug ID: 24599 Summary: Add endpoints for bulk processing of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com As highlighted by bug 24410, we need a way to handle bulk submission of holds via the API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23669] New: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23669 Bug ID: 23669 Summary: Verify if checkouts or reserves requests from ILS-DI periods overlap with existing reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: julian.maurice(a)biblibre.com Depends on: 15261, 23531 Same as BZ15261 but for WebServices Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 [Bug 15261] Verify if checkouts or reserves requests periods overlap with existing reserves https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23531 [Bug 23531] ILS-DI doesn't implement needed_before_date and pickup_expiry_date parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 16791] New: Explanation of callnumber.pl plugin
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16791 Bug ID: 16791 Summary: Explanation of callnumber.pl plugin Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: eb(a)efdss.org QA Contact: testopia(a)bugs.koha-community.org Perhaps a brief explanation of what callnumber.pl is meant to do would be a useful addition to the manual. I am not certain what its function is, though I discovered that it doesn’t do what I was hoping it would. See bug 13615 for a long winded query. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29188] New: Expired serial subscriptions can still receive issues
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29188 Bug ID: 29188 Summary: Expired serial subscriptions can still receive issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the manual, it says "If your serial subscription has expired you won’t be able to receive issues." But that is not actually true. Expired subscriptions can still generate new issues and you can still receive them. To stop a subscription from generating new issues, you have to close it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30618] New: Important and mandatory select fields not highlighted on additem.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30618 Bug ID: 30618 Summary: Important and mandatory select fields not highlighted on additem.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If one tries to add an item and mandatory or important select field isn't filled, field isn't highlighted like input fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28546] New: Framework default value special var for year in Manual
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28546 Bug ID: 28546 Summary: Framework default value special var for year in Manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org There is a mistake (or change) in framework default value special vars. In manual : There are several values that you can use here that will be replaced automatically when a new record is created: <<MM>> - the current month, 2 digits <<DD>> - the current day of month, 2 digits <<YEAR>> - the current year, 4 digits <<USER>> - the username of the currently logged in user For example: a default of "<<MM>>/<<DD>>/<<YEAR>>" (without quotes) will print the current date in the form of "01/21/2021" See https://gitlab.com/koha-community/koha-manual/-/blob/master/source/administ… But in Koha code in cataloguing/addbiblio.pl : $value =~ s/<<YYYY>>/$year/g; $value =~ s/<<YY>>/$shortyear/g; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28501] New: Document how to use the search configuration page
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '25

22 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28501 Bug ID: 28501 Summary: Document how to use the search configuration page Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Keywords: Manual Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In the manual there is currently no information on how to use the search configuration page for Elasticsearch. I am especially thinking of: - How to add a field/subfield to an existing index - How to create a new index to use for search -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2