Details
Assignee
UnassignedUnassignedReporter
(OLD ACCOUNT) Erin Nettifee(OLD ACCOUNT) Erin NettifeePriority
TBDDevelopment Team
Core: PlatformRCA Group
TBDTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
(OLD ACCOUNT) Erin Nettifee
(OLD ACCOUNT) Erin NettifeePriority
Development Team
Core: Platform
RCA Group
TBD
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 9, 2022 at 2:14 PM
Updated November 9, 2022 at 2:34 PM
Overview:
This is being observed on Nolana-bugfest; I'm filing it as a bug, but it may not actually be a bug but rather just something that is an artifact of data issues on that environment.
A user reported that they were unable to edit permissions on their account - when they tried to do so, they got the following error message:
Some research suggests that that permission existed in Fameflower and prior but was removed as part of — so, two years ago.
A GET call to /perms/permissions suggests that ui-finance.all still exists as a reference in two permission sets - "phenomenal cosmic powers" and "fse_admin". "Phenomenal cosmic powers" is, in itself, a child of folio_admin.
(JSON of the permissions on bugfest-nolana:
)
If you view "phenomenal cosmic powers" in the permissions user interface, ui-finance.all doesn't show up. That makes sense.
Using Postman, I tried to do a PUT to
/perms/permissions/6d06d2a3-3b85-45e8-b8de-dc3638fbbfc5
to see if I could remove ui-finance.all, and I get the same error message from the UI:
I understand that there is recent code to prevent assignment of permissions in FOLIO that don't exist, but is that then preventing the removal of this permission?
This is not preventing Bugfest work, as people can simply create new users with new permission sets, but I think it would be good to understand what is happening here.
Interested parties: