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

[Bug 30217] New: When an item waiting on hold for one patron is checked out to another the hold is reverted but not logged
by bugzilla-daemon＠bugs.koha-community.org 01 May '24

01 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30217 Bug ID: 30217 Summary: When an item waiting on hold for one patron is checked out to another the hold is reverted but not logged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Enable Holds log 2 - Place a hold for a patron 3 - Check in the item and confirm hold to mark waiting 4 - Check the logs - you see the create and modify actions 5 - Checkout the item to a different patron 6 - The hold is no longer marked waiting 7 - Check the logs - no modification for the reversion of waiting status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 35491] New: Reverting waiting status for holds is not logged
by bugzilla-daemon＠bugs.koha-community.org 01 May '24

01 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35491 Bug ID: 35491 Summary: Reverting waiting status for holds is not logged 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should capture the modification of the hold when this is done -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 36177] New: We need selenium tests to cover csrf checks
by bugzilla-daemon＠bugs.koha-community.org 01 May '24

01 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36177 Bug ID: 36177 Summary: We need selenium tests to cover csrf checks 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 36148 will be adding a check in our middleware for csrf coverage on post operations - we need selenium tests to cover all scenarios -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 35614] New: Update cpanfile for Mojolicious::Plugin::OpenAPI v5.09
by bugzilla-daemon＠bugs.koha-community.org 01 May '24

01 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35614 Bug ID: 35614 Summary: Update cpanfile for Mojolicious::Plugin::OpenAPI v5.09 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Work to be done: - Update cpanfile - JSON::Validator 5.13 is required as well - Build that version on the staging Debian repo for regression testing - Push to stables -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 32971] New: Access to ERM module requires 'erm' permission and 'vendors_manage' acquisition sub-permission
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '24

30 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32971 Bug ID: 32971 Summary: Access to ERM module requires 'erm' permission and 'vendors_manage' acquisition sub-permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: pedro.amorim(a)ptfs-europe.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, tomascohen(a)gmail.com Depends on: 32968 To reproduce: - Enable ERMModule - Login as a staff member that only has 2 permissions: -- catalogue (required for staff login) -- erm - Access erm page, check the 403 forbidden error This happens because ERM module is requesting the /api/v1/acquisitions/vendors api endpoint which in turn requires the vendors_manage sub-permission (see acquisitions_vendors.yaml). If you enable the acquisition vendors_manage sub-permission for that user, you're able to confirm that you can now access the ERM module as expected. Ideally, having just the 'erm' permission should be enough to be granted access to ERM. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32968 [Bug 32968] Create granular permissions for ERM -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 34634] New: Expiration date does not display on /reserve/request.pl if date is today or in the past
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '24

30 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34634 Bug ID: 34634 Summary: Expiration date does not display on /reserve/request.pl if date is today or in the past 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Place some holds and go to /reserve/request.pl for that bib. 2. If the reserves.expirationdate is set to today or some date in the past the date does not display in the Flatpickr instance. 3. Change the reserves.expirationdate to sometime in the future, the date displays. If staff cannot edit the reserves.expirationdate because it is in the past it still needs to display. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 21246] New: Extend the 'Last patron' navigation feature to 'Last X patrons'
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '24

30 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21246 Bug ID: 21246 Summary: Extend the 'Last patron' navigation feature to 'Last X patrons' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 A proposed enhancement during QA of bug 20312 was to expand it's functionality to become a short last of the last X patrons rather than just the last 1 patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 35428] New: gulp po tasks do not clean temporary files
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '24

30 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35428 Bug ID: 35428 Summary: gulp po tasks do not clean temporary files Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: translate.koha-community.org Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org gulp po:update will generate 1 /tmp/koha-* directory per task. We need to remove them when the script does not longer need them. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 31656] New: Expand TT access for CHECKOUT notice
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '24

29 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31656 Bug ID: 31656 Summary: Expand TT access for CHECKOUT notice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The FOREACH loop TT syntax doesn't work in the CHECKOUT notice. I suspect this is due to it being generated in C4/Circulation.pm, as described here https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_S… You can only use four dashes to repeat information in this notice. To test: 1. Edit the CHECKOUT notice 1.1. Go to Tools > Notices and slips 1.2. Search for the CHECKOUT notice and click Edit 1.3. In the Email tab, use the following code for the letter (should be the one by default) The following items have been checked out: ---- [% biblio.title %] ---- Thank you for visiting [% branch.branchname %]. 1.4. Save 2. In a patron file, choose to get the Item checkout email notice 2.1. Go to a patron file 2.2. Click on the Edit button next to the patron messaging preferences table 2.3. Check Email for the Item checkout 2.4. Save 3. Check out items to the same patron 3.1. Go to the Check out tab in the patron file 3.2. Check out at least two items 4. Check the generated notice 4.1. Go to the Notices tab in the patron file 4.2. Click on the Checkouts notice to view the contents --> It should show both titles 5. Change the CHECKOUT notice, redo steps 1.x using the following letter content The following items have been checked out: [% FOREACH checkout IN checkouts %] [%~ SET item = checkout.item %] [%~ SET biblio = checkout.item.biblio %] [% biblio.title %] [% END %] Thank you for visiting [% branch.branchname %]. 6. Try checking out again, redo steps 2-4 with a different patron --> There are no titles and the letter is repeated twice -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 20705] New: In subscription, subscription length type "month" do not show right number of issues on prediction pattern
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '24

29 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20705 Bug ID: 20705 Summary: In subscription, subscription length type "month" do not show right number of issues on prediction pattern Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 Created attachment 75025 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=75025&action=ed… prediction pattern Hi, When we choose "month" in subscription lenght type and I enter "12", only one issues is shown in prediction pattern. If i choose "issues" in SLT, exact number of issues is displayed in prediction pattern. Why it does not work with months even if I choose monthly for frequency. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3