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

[Bug 22780] New: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22780 Bug ID: 22780 Summary: MarkLostItemsAsReturned - map to Lost-sttaus instead of context where the transaction took place 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: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Syspref MarkLostItemsAsReturned is mapped to the context where you make the transaction - Holds to pull list, longoverdue cronjob et.c. I can't see any logical reason for this! I think it would be better to map to Lost-statuses: Lost = don't mark as returned Longoverdue = don't mark as returned Lost and paid for = mark as returned et.c. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 34346] New: Adding duplicate tag to a framework leads to error page, should give user readable error message
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34346 Bug ID: 34346 Summary: Adding duplicate tag to a framework leads to error page, should give user readable error message Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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: gmcharlt(a)gmail.com I tried adding a tag to the default framework and got a 500 error. It was because the tag already existed. Elsewhere in Koha, we get a user readable message saying something like "An error occurred when inserting this patron category. The patron category might already exist." To replicate: 1. In the staff interface, go to Administration > MARC bibliographic framework 2. Click the Actions button next to the default framework and choose MARC structure 3. Click New tag 4. Fill out the form to add an already existing tag number Tag: 699 Label for lib: Local subject Label for OPAC: Local subject 5. Click Save changes --> 500 error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 33453] New: Confirmation button for 'Record cashup' should be yellow
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33453 Bug ID: 33453 Summary: Confirmation button for 'Record cashup' should be yellow 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When recording a cashup the confirmation button in the modal should be 'yellow' for the primary action. * Enable cash registers and create a cash register * Go to Tools > Transaction history for ... * Click on 'Record cashup' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 32313] New: Complete database column descriptions for cataloguing module in guided reports
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32313 Bug ID: 32313 Summary: Complete database column descriptions for cataloguing module in guided reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 32292, 29695 There are entries missing for the biblioitems table. Bug 32292 takes care of missing entries in biblio and items. How to test: * Add a new guided report * Select module catalog * Verify that statistics is missing some descriptions, only showing the database value Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29695 [Bug 29695] Centralize columns' descriptions https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32292 [Bug 32292] Update and add database column descriptions used in guided reports -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 25520] New: Change wording on SMS phone number set up
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25520 Bug ID: 25520 Summary: Change wording on SMS phone number set up 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The wording in the staff interface when a staff member is adding an SMS number is confusing. Could we show two different formats to enter a phone number? For example: SMS number should be in the format 9876543210 or +11234567890 On the OPAC, I believe it looks clearer to users: Please enter numbers only. (123) 456-7890 would be entered as 1234567890. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 24424] New: Advanced editor - interface hangs as "Loading" when given an invalid bib number
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24424 Bug ID: 24424 Summary: Advanced editor - interface hangs as "Loading" when given an invalid bib number 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: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The Advanced Editor hangs with "Loading, please wait" message when given an invalid bib number /cgi-bin/koha/cataloguing/editor.pl#catalog/55555 https://paste.pics/e7c7e4956dfa888b13b54332472df066 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 32696] New: Recalls can inadvertently extend the due date
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32696 Bug ID: 32696 Summary: Recalls can inadvertently extend the due date Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is due sooner than the recall due date interval then placing a recall on it can inadvertently extend the book's due date, possibly causing the recalling patron to receive the item later than they would otherwise. To recreate the issue: - turn on recalls with UseRecalls and scaffold out the minimal circulation rules needed to use the feature - set the recall due date interval to 7 days or any other arbitrary period - check out an item to one patron & set the due date to be before the recall due date interval will have elapsed (e.g. the next day) - as a second patron, place a recall on the item in question Actual behavior: the item's due date is extended to the current date plus the recalls due date interval. Desired behavior: the item's due date should stay the same so the recalling patron doesn't face an additional delay in obtaining it. The logic is that the new due date should be either the existing due date or the current date plus the recall due date interval, whichever is sooner. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 30493] New: Pending archived suggestions appear on intranet home page
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30493 Bug ID: 30493 Summary: Pending archived suggestions appear on intranet home page 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org If suggestions are archived before their status is changed to something other than "Pending", they still appear on the intranet home page and the acquisitions home page as suggestions to be managed. 1. Go to Acquisitions > Suggestions 2. Click on New purchase suggestion 3. Fill in the form (title only is fine) 4. Click on Submit your suggestion 5. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 6. Go to Acquisitions --> Notice it says that there is 1 pending suggestion 7. Go to Suggestions 8. Click on the up arrow to the right of the Edit button and choose Archive --> There are no more pending suggestions 9. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 10. Go to Acquisitions --> Notice it says that there is 1 pending suggestion -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 30715] New: Terminology: Logs should use should use staff interface and not intranet for the inrerface
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30715 Bug ID: 30715 Summary: Terminology: Logs should use should use staff interface and not intranet for the inrerface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When logs are enabled and an action is performed in the staff interface, it is displayed in the log interface column as "Intranet". This should be displayed as "Staff interface", as per the terminology guidelines: https://wiki.koha-community.org/wiki/Terminology#I To reproduce: 1. Any action logged by the staff interface should show this in the log viewer. 2. Example: . Enable logs for cataloging (enabled by default in koha-testing-docker) (CataloguingLog system preference). . For a record, change the shelving location for any item to something else. . Check the logs (Tools > Additional tools > Log viewer then Submit). . The interface column shows that the change was made in the "Intranet". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 30372] New: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30372 Bug ID: 30372 Summary: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Testing bug 30120 I noticed that when you lave a mandatory extended patron attribute (or possibly another mandatory field) empty, all values already entered in extended attributes will be removed when clicking submit. To test: - Activate patron self registration without email verification - Create several patron attributes as visible and editable in the OPAC, make one mandatory - Register as a new patron from the OPAC - Fill in all required fields but the extended attribute - Submit - Verify that the contents of the other extended attribute fields have been removed and you are forced to re-enter -- You are receiving this mail because: You are watching all bug changes.

1 14