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

[Bug 30349] New: cleanup bulkmarcimport.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30349 Bug ID: 30349 Summary: cleanup bulkmarcimport.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: davewood(a)gmx.at QA Contact: testopia(a)bugs.koha-community.org the help page of bulkmarcimport.pl doesnt use double dashes for multi-character options. Id like to update the help info and add multi-character options where they are missing. (e.g. --help for -h) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 29440] New: Refactor/clean up bulkmarcimport.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29440 Bug ID: 29440 Summary: Refactor/clean up bulkmarcimport.pl 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In order to address various issues with and add some new features to bulkmarcimport.pl I found it necessary to first clean up the script. At our library we run a modified version of bulkmarcimport.pl that for practical reasons was squashed into one commit. I have split this commit into various feature branches, all which depends on the clean up version of the script. So in the first commit of this issue I tried to isolate all the changes that should not affect current script behavior and are mostly related to code formatting, structure and optimizations. The next commits (for this issue) will contain changes that do affect script behavior, but that I would argue should be the default behavior and where the current could be considered confusing and/or buggy. I will later create new related issues for the newly added features mentioned above (and it's possible there is stuff in this patch that should have been broken out and I have overlooked). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 132

[Bug 29510] New: objects.find should call search_limited if present
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29510 Bug ID: 29510 Summary: objects.find should call search_limited if present Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 34479] New: Clear saved patron search selections after certain actions
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34479 Bug ID: 34479 Summary: Clear saved patron search selections after certain actions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: cslone(a)camdencountylibrary.org, gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, testopia(a)bugs.koha-community.org Depends on: 29971 +++ This bug was initially created as a clone of Bug #29971 +++ (In reply to Chris Slone from comment #17) > I think this is a problematic implementation, as it seems to be retaining > the selected patrons even after you perform a function (merge patrons, > create a list, do a batch edit) and do a completely new search. This means > that the previously selected patrons remain selected even when it doesn't > really make logical sense. It's great to be able to select multiple patrons > across different searches, but doing something like merging accounts should > absolutely clear out that selection. > > It seems to already be causing some issues, see this ticket: > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34262 > > We've also had some errors at our library from this (before we realized what > was happening). I'm moving this issue into a new bug report because we don't re-open bugs for features which have been pushed. This will let us have a discussion about refining the behavior. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29971 [Bug 29971] Remember selections across patron search pages -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 28664] New: One should not be able to issue a refund against a VOID accountline
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28664 Bug ID: 28664 Summary: One should not be able to issue a refund against a VOID accountline Change sponsored?: --- Product: Koha Version: master 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 CC: andrew(a)bywatersolutions.com, kyle(a)bywatersolutions.com, sally.healey(a)cheshiresharedservices.gov.uk, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 27971 Blocks: 13985 When adding the VOID account line type in bug 27971 I neglected to update the logic for the display of the 'Issue refund' button on the patron transactions page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] Cash Management - Koha as 'Point of Sale' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27971 [Bug 27971] The VOID method should be updated to respect double-entry accounting -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 35026] New: Refactor addorderiso2709.pl to use object methods
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35026 Bug ID: 35026 Summary: Refactor addorderiso2709.pl to use object methods 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org As part of the process to be added in bug 34355, the addorderiso2709.pl script should be refactored to make use of object methods that can then be re-used in a cron script for bug 34355 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 141

[Bug 34608] New: Add sort1 and sort2 to patron search results
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34608 Bug ID: 34608 Summary: Add sort1 and sort2 to patron search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would like the option of showing columns for sort1 and sort2 to patron search results. -- You are receiving this mail because: You are watching all bug changes.

1 53

[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 34585] New: "When to charge" columns value not copied when editing circulation rule
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34585 Bug ID: 34585 Summary: "When to charge" columns value not copied when editing circulation rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org When one tries to edit circulation rule "When to charge" columns value is always set as "End of interval". This happens because column doesn't have data-code attribute which defines existing rules value. To reproduce: 1. Navigate to Circulation and fine rules page. 2. Find or create a rule with a "When to charge" value set as "Start of interval". 3. Edit rule. => Note that "When to charge" value is now "End of interval", while as the other values should be copied as they were. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27