Permissions: Order settings perms do not allow create new reason for closure

Description

Overview: User with all order and order settings permissions is not able to create new Reasons for closure in the settings area

Steps to Reproduce:

  1. Log into some FOLIO environment as User X

  2. Create user and assign permission Settings (Orders): Can view and edit all settings

  3. Login in new user

  4. navigate to order settings

  5. select "Closing purchase order reasons"

Expected Results: View in third pane displays all reasons for closure. "New" button appears in top right. User can click new and save a new reason for closure to the list

Actual Results: View in third pane displays all reasons for closure. "New" DOES NOT appears in top right.

Additional Information:
URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

User super admin user

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges March 21, 2023 at 9:49 PM

Test successful in bugfest-orchid

NinaChistova March 17, 2023 at 12:08 PM

Verified on https://bugfest-orchid.int.aws.folio.org/

Works as expected

could you please review? Thanks!

JenkinsNotifications March 17, 2023 at 9:56 AM

Deployed to Orchid bf env. Moved status to In bugfix review from status Awaiting deployment. Please proceed with verification

Dennis Bridges March 16, 2023 at 10:05 PM

Test successful in folio-snapshot.

NinaChistova March 15, 2023 at 6:46 AM

Hello  

Verified on https://bugfest-orchid.int.aws.folio.org/ - no "New" button for user with "Settings (Orders): Can view and edit all settings" permission (but yes, it works as expected for the same user on Snapshot env)

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

Release

Orchid (R1 2023) Bug Fix

RCA Group

Missing module permission

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 14, 2023 at 3:18 PM
Updated March 21, 2023 at 9:49 PM
Resolved March 16, 2023 at 10:05 PM
TestRail: Cases
TestRail: Runs