Bug 40912 - Receive shipments button requires full acquisitions permissions not just order_receive
Summary: Receive shipments button requires full acquisitions permissions not just orde...
Status: RESOLVED DUPLICATE of bug 40868
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low major
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 38010
Blocks:
  Show dependency treegraph
 
Reported: 2025-09-30 16:19 UTC by Brendan Lawlor
Modified: 2025-09-30 16:30 UTC (History)
6 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brendan Lawlor 2025-09-30 16:19:09 UTC
The permission check to display the Receive shipments button in the Vendors table and  Vendors page requires full acquisitions permissions. (Any route like koha/acquisition/vendors) It doesn't just check just for the sub permission order_receive.

From VendorShow.vue line 48:

<ToolbarButton
                v-if="
                    vendor.active &&
                    vendor.baskets_count > 0 &&
                    isUserPermitted('CAN_user_acquisition_order_receive')
                "
                :to="{
                    path: '/cgi-bin/koha/acqui/parcels.pl',
                    query: { booksellerid: vendor.id },
                }"
                icon="inbox"
                :title="$__('Receive shipments')"
                callback="redirect"
            />

This looks like it should work to check for the order_receive sub permission, but it only renders when the user has full acquisitions permissions.

This is similar to bug 40684, so my guess is it needs a similar fix in /api/v1/swagger/paths/acquisitions_orders.yaml
Comment 1 Brendan Lawlor 2025-09-30 16:30:32 UTC

*** This bug has been marked as a duplicate of bug 40868 ***