Requests (UXPROD-790)

[UXPROD-1808] Requests Permissions (Basic CRU) Created: 26/Jun/19  Updated: 16/Sep/20  Resolved: 06/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: cap-mvp, po-mvp, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UIREQ-307 Permissions - Requests: View, edit, c... Closed
is defined by UIREQ-107 Permissions - Requests: View Closed
is defined by UIREQ-108 Permissions - Requests: View, edit, c... Closed
is defined by UIREQ-109 Permissions - Requests: View, create Closed
Relates
relates to UXPROD-236 Requests Permissions (Advanced/Action... Closed
Potential Workaround: Cate Boerema: Workaround is to give everyone who needs access to Requests the existing "Requests: All" permission which means they can create, read, update and cancel requests. Note: there isn't much that can be updated on a request (only expiration dates and fulfillment options)
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Cate Boerema (Inactive)
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: CB: Assumption is no backend work is needed for this
Development Team: Vega
PO Rank: 96.2
PO Ranking Note: 2019-07-12: Increased rank significantly because, per SIG discussion, my impression is that this is very important for many institutions. Calculated rank is currently very low because it hasn't been ranked by many.
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Library administrators want to be able to give some staff limited access to requests so they can, for example, view requests without creating or editing them. FOLIO currently only offers a single all-or-nothing permission for the Requests app (Requests: All).

The focus of this feature is to implement more granular CRUD based permissions for Requests:

  • C: "Requests: Can create request". Will not include ability to edit in this case.
  • R: "Requests: Can view requests"
  • U: "Requests: Can edit requests". This will include the ability to cancel


 Comments   
Comment by Cate Boerema (Inactive) [ 02/Jul/19 ]

RA SIG discussed this in feature re-ranking. See discussion at 42:29 here: https://drive.google.com/file/d/15RbACU90Ln4JAazWSz0iM4ZSYia6mIaK/view?usp=sharing

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