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

[Bug 20028] New: Export all petron related personal data in one package
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 Bug ID: 20028 Summary: Export all petron related personal data in one package 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: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, josef.moravec(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle.m.hall(a)gmail.com, magnus(a)libriotech.no, mirko(a)abunchofthings.net, paul.poulain(a)biblibre.com, rbit(a)rbit.cz Blocks: 18081 At least in CVS, maybe in JSON or other machnine readable formats. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18081 [Bug 18081] [omnibus] GDPR (General Data Protection Regulation) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 88

[Bug 19037] New: Circulation and fine rules test tool
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19037 Bug ID: 19037 Summary: Circulation and fine rules test tool 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: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Add a test tool for circulation and fine rules. The point of the tool is to display the effective issuing rule that matches item, patron and branch. Add a REST API endpoint to query effective issuing rules by given parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 27176] New: Using z39.50 with Advanced Editor if fields are out of order, they also display out of order
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27176 Bug ID: 27176 Summary: Using z39.50 with Advanced Editor if fields are out of order, they also display out of order Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a library uses the z39.50 search through the Advanced editor and imports a record that has marc fields out of order, such as having a 700 field listed first, followed by the 245, then the 008. Importing this record will display the fields out of order in the advanced editor. There is no easy way to re-order these fields in the advanced editor module, but it can be done through the clipboard. Using the basic editor, importing the same file with fields out of order will import correctly. If this record is saved, and then re-opened in the Advanced Editor, the fields are ordered correctly. It would be convenient and consistent to have fields ordered when importing a record through both the advanced editor and the basic editor. A workaround to the library that has imported (through the Advanced Editor) one of these records that have marc fields out of order. Once this record has been saved to Koha, reopened in the Basic Editor, and then opened through the Advanced Editor- the fields will be in the correct order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28849] New: Claim Returned should alert at checkout
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '26

10 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28849 Bug ID: 28849 Summary: Claim Returned should alert at checkout Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Depends on: 14697 When checking out an item connected to an unresolved claim, we should alert the user just as we do at checkin. To recreate: - Set ClaimReturnedLostValue - set MarkLostItemAsReturned so that claimed items are marked as returned - check an item out to Patron A - mark that item claimed - check the item out to Patron B - Koha alerts you that it's removed the lost status, but not that there is an unresolved claim - set MarkLostItemAsReturned so that claimed items are NOT marked as returned - mark item as claimed on Patron B's account - check the item out to Patron C - Koha alerts you that the it's removed the item's lost status and asks if you want to end Patron B's checkout, but does not mention the 2 unresolved claims - check the item in - Koha gives a return-claim dialog alert with links to Patron A and Patron B We should give the same alert at checkout, since that's the moment at which Koha first knows this item has been found. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 [Bug 14697] Extend and enhance "Claims returned" lost status -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 16982] New: add edi account to new menu on vendor page
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16982 Bug ID: 16982 Summary: add edi account to new menu on vendor page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: nengard(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if you could jump to creating a vendor account from the vendor menu. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 30113] New: kohaTable add_filters option should be renamed to show_filter_row
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30113 Bug ID: 30113 Summary: kohaTable add_filters option should be renamed to show_filter_row 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The 'add_filters' option available to us on the ajax dataTables wrapper, kohaTable, is used to enabled/disable the presence of the search filters row displayed at the top of the datatable. We should rename the option to clarify it's intended use... add_filters is too generic and could mean a number of things. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 24320] New: Remove ending . from XSLT result templates
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24320 Bug ID: 24320 Summary: Remove ending . from XSLT result templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Same as bug 22884, but for the standard XSLT result list templates: I think the end user doesn't need the . at the end and it is more irritating then helpful, especially since we are very inconsistent in printing it. I think either we rely on libraries adding the punctuation or let Koha add it, but mixing both is not good. I suggest to remove the . where we are currently adding it for display. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 25284] New: Can't open /var/log/koha/kohadev/opac-error.log (Permission denied)
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25284 Bug ID: 25284 Summary: Can't open /var/log/koha/kohadev/opac-error.log (Permission denied) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I have completely rebuilt my kohadevbox, but can't get rid of this error: Can't open /var/log/koha/kohadev/opac-error.log (Permission denied) at /usr/share/perl5/Log/Log4perl/Appender/File.pm line 143 First it appeared when I was trying to save system preferences. Now I ran into it, when trying to check out an item. I have no idea what's causing this and if this is a general or a kohadevbox issue. Help appreciated! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 18787] New: Create permission profils for staff user
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18787 Bug ID: 18787 Summary: Create permission profils for staff user Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would very useful if we could define different permission profils, depending on the library uses, to prefill permissions. For example, in our site, we could have : - a "catalog profil" to edit records and items - a "subscription profil" because there is a team which works specifically on periodical publications - a "circulation profil" because some of us don't work directly with patrons so they don't need to access to the Patron and Circulation module (but they could borrow books for themselves) - a "team manager profil" because they have permission to see acquisition budget for all their team - etc. It would be an easier way to define permissions for a new staff user and a way to be sure all the accounts are identically set. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 24180] New: maintain separate repeated subfields when linking authority in advanced catalog editor
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '26

09 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24180 Bug ID: 24180 Summary: maintain separate repeated subfields when linking authority in advanced catalog editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To test: - create an authority record with two 150$z fields - create a new bib in the advanced editor - link your bib to your authority - note your two $z subfields have been concatenated Tested this on master with specifically a topical term authority linking to a 650, though I don't suspect those details will make a difference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12