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

[Bug 22180] New: SERIAL_ALERT email does not send if the status is Claimed before becoming Arrived.
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '24

26 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22180 Bug ID: 22180 Summary: SERIAL_ALERT email does not send if the status is Claimed before becoming Arrived. Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- Hi, SERIAL_ALERT email sends itself correctly when the status of the issue changes from Expected to Arrived. But the issues goes from Expected to Claimed and then to Arrived, the email does not send. I also tested it with other status. Only the way Expected> Arrived works. Is it normal? Version tested: 18.05.04 REgards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 32924] New: Filter agreements by logged in librarian
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '24

26 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32924 Bug ID: 32924 Summary: Filter agreements by logged in librarian Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 32030 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 19764] New: possibility to sort list by decreasing date
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '24

25 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19764 Bug ID: 19764 Summary: possibility to sort list by decreasing date Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would nice if in a list at the OPAC to had the possibility to sort by decreasing date and vice versa. Actually, we can only sort by ascending copyright date and it would be graete for the user to have the possibility to chose ascending ou decreasing date. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23608] New: Koha::Objects::Limit::Library->get_library_limits can return undef
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '24

25 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23608 Bug ID: 23608 Summary: Koha::Objects::Limit::Library->get_library_limits can return undef Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 get_library_limits routine within Koha::Objects::Limit::Library can return either a Koha::Libraries set or undef at present. As this is often part of a method chain we should drop the requirement to always check for undef in the return and instead ensure we return an unfiltered Koha::Libraries set which can be relied upon in subsequent method chaining. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 28129] New: Allow staff to add subscription alerts on behalf of patrons
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '24

25 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28129 Bug ID: 28129 Summary: Allow staff to add subscription alerts on behalf of patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment email alerts for new issues of a subscription can only be managed by the patron themselves through the OPAC. And there only from the detail pages of the serials. It would be nice if it would be possible to delete (see bug 25848), but also to add these email notifications on behalf of patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26344] New: Move translatable strings out of templates into patrons.js
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26344 Bug ID: 26344 Summary: Move translatable strings out of templates into patrons.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 21156 Strings defined in templates for use in autocomplete/patrons.js can now be wrapped in the new translation function. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21156 [Bug 21156] Internationalization: plural forms, context, and more for JS files -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 27354] New: Translate JavaScript in intranet-tmpl/js
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27354 Bug ID: 27354 Summary: Translate JavaScript in intranet-tmpl/js Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Blocks: 26344 Currently JavaScript files in intranet-tmpl/js are not processed for translation. This makes it impossible to leverage the new I18N tools created by 21156. I don't think there's any reason why this directory should be excluded. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26344 [Bug 26344] Move translatable strings out of templates into patrons.js -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 27028] New: Transfers: hold warning doesn't display patron's name and their branch
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27028 Bug ID: 27028 Summary: Transfers: hold warning doesn't display patron's name and their branch 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: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 113641 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113641&action=e… screenshot-of-the-issue == Test plan == 1. Place a hold (record level in my example) 2. Try a transfer 3. Get a hold warning 4. It doesn't display (at least, not checked everything) the patron's name and their branch. See screenshot-of-the-issue.png The code confirms that it should: Reserve found for [% name | html %] (<a href="/cgi-bin/koha/members/moremember.pl?borrowernumber=[% borrowernumber | uri %]">[% borrowernumber | html %]</a>). [...] [% IF ( reserved ) %]Set reserve to waiting and transfer book to [% branchname | html %]: [% END %] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 19375] New: Show message when transfer is finished by checking in
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19375 Bug ID: 19375 Summary: Show message when transfer is finished by checking in 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When book is in transfer and is in transfer and is checked in in target library, the transfer is finished by this operation. It would be nice to have some message about that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31184] New: Add default permissions by patron category
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '24

24 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31184 Bug ID: 31184 Summary: Add default permissions by patron category 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It could be useful to assign default permissions by patron category. (This was pointed out to me by a librarian who had similar functionality in a previous system.) Alternatively, I suppose we could create "permission profiles" and assign those at patron creation time I suppose. The idea being that you set up permissions for certain staff categories (like cataloguing or circulation) and then the staff automatically have their permissions set up and don't require you to manually check all the right checkboxes on a per-user basis. (I suppose role/group-based authorization would cut down even further on having to manually manage so many permissions...although this probably more of a problem for large libraries than small libraries...) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5