[UXPROD-3176] Do not allow FOLIO user-created permission sets to have the same display name as another user-created permission set Created: 12/Jul/21  Updated: 07/Jul/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Amelia Sutton
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2021-07-12-10-20-58-207.png    
Issue links:
Defines
is defined by UIU-2689 Prevent duplicate permission names in... Open
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R2
Rank: MO State (MVP June 2020): R4

 Description   

Current situation or problem:

Permission sets can be created in Settings > Users > General > Permission Sets that have the same display name. This can lead to a lot of confusion in environments where multiple individuals have the ability to create permission sets.

In scope

  • Add a check on General Information > Permission set name such that a FOLIO user cannot create a permission set (e.g., a permission with mutable=true) with the same permission set name as a permission set (permission with mutable=true) that already exists in the system.

Out of scope

  • Adding a check on Permission set name collision with system-defined permissions, since a filter exists in the UI to allow for distinguishing between the two. If you have a permission set named "A" and a permission named "A", you are able to tell what you are looking at because of the column for permission type. In other words, we only need to check permission name uniqueness against permissions where mutable = true.

Use case(s)

  • A library has multiple branches, and there is a staff member at each branch that can create permission sets. Each branch creates a permission set called "Circulation desk", but one branch includes the ability to mark items missing, and the other does not. Without this feature, staff at each branch won't know which permission set corresponds to their branch.

Proposed solution/stories
UIU-2689 Open

Links to additional info

Questions

  • Is it necessary to also prohibit this through the API? Or is it enough to know that mutable permissions are almost always only created through the UI, and since that's where we are concerned about name collisions, that's where we do the work?


 Comments   
Comment by Erin Nettifee [ 12/Jul/21 ]

patty.wanninger this came up in the PO channel so I created a feature for it. This might be a ui-only candidate, Khalilah Gambrell?

Comment by Erin Nettifee [ 07/Jul/23 ]

Hi Amelia Sutton - this has been hanging around for a bit, so I am assigning it to you just so you have some awareness. I do think there should be some discussion about whether this duplication issue needs to also be prevented in the API, or if it is enough for it to be prevented from happening in the UI.

Generated at Fri Feb 09 00:29:57 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.