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

[Bug 8838] Digest option for HOLD notice
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '23

21 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 Cheryl <clackman(a)fargolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clackman(a)fargolibrary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23207] New: Allow automatic checkin/return at end of circulation period
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23207 Bug ID: 23207 Summary: Allow automatic checkin/return at end of circulation period Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Libraries with materials like Museum Passes, Seed Libraries, and so forth, would like the option have have certain materials checked in/returned from a patron's account on the due date. For example, a library checks out a Museum pass to a patron - it is not a physical item that needs to be returned, but they only want the patron to be able to have one of them during a seven-day period. Right now these items have to be manually checked in at the end of the circ period to remove it from the patron account. An automatic return option via cron job would be helpful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 32725] New: Be able to nested sets of conditions in MARC Modification templates
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32725 Bug ID: 32725 Summary: Be able to nested sets of conditions in MARC Modification templates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It be useful in MARC Modification templates to have nested sets of conditions : If XXX then If YYYY then If ZZZZ then -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32724] New: Merge fields / subfields with MARC modification templates
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32724 Bug ID: 32724 Summary: Merge fields / subfields with MARC modification templates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be very usefull to be able to merge some fields or subfields, acccording to a specific subfield value, with MARC modification templates. For example, XXX$a= tata XXX$5= number YYY$a = toto YYY$5 = number merge XXX$a and YYY$a in ZZZ$a if XXX$5=YYY$5 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34060] New: Broken formatting of resource_list items on mobile in OPAC
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34060 Bug ID: 34060 Summary: Broken formatting of resource_list items on mobile in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 152476 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=152476&action=e… Tablet screenshot showing the odd formatting When browsing the OPAC on an iPad the last item in some "resource_list" ul elements go out of alignment vertically. We've only been able to replicate this on the tablet itself and it happens in both Safari and Chrome. The problem does not appear when resizing the browser window on a computer. It seems to be a disagreement with the last-child:after rule that replaces the pipe character with nothing: .resource_list li:last-child:after {content: '';} As a workaround, replacing the pipe character with a space instead of nothing seems to avoid the problem: .resource_list li:last-child:after {content: ' ';} -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34040] New: Add option to limit fund usage to branch or group
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34040 Bug ID: 34040 Summary: Add option to limit fund usage to branch or group Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org While you can limit who can edit funds, it doesn't limit who can use a fund in a basket. It would be very helpful for consortia, who may have a large number of funds if there was maybe a permission or preference to only let staff use funds from their library or maybe their library group. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 30586] New: The fallback option when enabling MFA for login doesn't work
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '23

20 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30586 Bug ID: 30586 Summary: The fallback option when enabling MFA for login doesn't work 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 28786 We are missing the shared secret from the fallback display for when a user cannot use a QR scanner when enabling 2FA. I'm not sure how wise it is to display it in full text immediately anyway, perhaps it should be hidden by default.. but as it is, I can't see how the fallback would ever work.. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28786 [Bug 28786] Two-factor authentication for staff client - TOTP -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20478] New: Advance notices: send separate digest messages per branch
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '23

19 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20478 Bug ID: 20478 Summary: Advance notices: send separate digest messages per branch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org Current behavior for advance_notices.pl is to send one digest message for each borrower. The sender for the message is then set to the branch where the borrower is registered, which can be different from the branch or branches on the issues in question. Desired behavior is that the sender address on the notice message is that of the branch of the issues in question. Thus, the solution is to generate digest messages per branch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 33592] New: Use drag&drop or sorting options for AutoEmailPrimaryAddress
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '23

19 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33592 Bug ID: 33592 Summary: Use drag&drop or sorting options for AutoEmailPrimaryAddress Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Depends on: 29046 With bug 29046 you can define the sequence the email fields are checked when searching for a valid email address. It would be nice if we could make the GUI a bit more inutitive by allowing to drag and drop for sorting like we can do it for the installed languages. It would also need the combination with checkbox to allow for not using some fields at all. We also have that for languages. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29046 [Bug 29046] Allow libraries to specify email order for "AutoEmailPrimaryAddress" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20640] New: Allow migrating a request between backends
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '23

19 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20640 Bug ID: 20640 Summary: Allow migrating a request between backends 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: martin.renvoize(a)ptfs-europe.com Currently, once an ILL request has started on a path in one backend it cannot be migrated to another. We should allow the status graph to be modified with 'MoveFrom' and 'MoveTo' methods allowing a request to be migrated from one backend to another when both backend support it (and when the request hasn't progressed sufficiently in one backend to prevent cancellation) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81