[UXPROD-3039] Add ui-checkout.viewRequests and ui-checkout.viewLoans Permission to ui-checkout.all permission set Created: 11/Apr/21 Updated: 18/Jun/21 Resolved: 18/Jun/21 |
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Brooks Travis | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | front-end, frontend, permission_set, permissions, ui-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Rank: MO State (MVP June 2020): | R3 | ||||||||||||||||
| Description |
|
Current situation or problem: The ui-checkout.all permission set does not currently include the permission ui-checkout.viewRequests or ui-checkout.viewLoans. These need to be added to that set. In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions
|
| Comments |
| Comment by Brooks Travis [ 18/Jun/21 ] |
|
I'm closing this as it seems that implementing this would explicitly contravene the purpose of adding the permissions in the first place. I think there needs to be a discussion about that implementation, as it is semantically confusing, but it doesn't make sense to take this approach to resolving the confusion. |