Requests (UXPROD-790)

[UXPROD-1839] Cancel Request Permission (Action-Based) Created: 02/Jul/19  Updated: 06/Sep/22

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: New Feature Priority: P4
Reporter: Cate Boerema (Inactive) Assignee: Tim Auger
Resolution: Unresolved Votes: 0
Labels: round_iv, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2022-09-06-11-20-33-111.png    
Issue links:
Defines
is defined by UIREQ-110 Permissions - Requests: Cancel reques... Open
Relates
relates to UXPROD-236 Requests Permissions (Advanced/Action... Closed
relates to UXPROD-1828 action-based permissions Closed
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Cate Boerema (Inactive)
Back End Estimate: Medium < 5 days
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: CB: Estimate assumes action-based permission feature is already available
Development Team: Volaris
PO Rank: 24
PO Ranking Note: 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Sometimes circulation staff need to cancel a request (because the request was cancelled by the patron, needed by course reserves etc). However, not all circ staff should have the permission to take this action.

The purpose of this feature is to create a permission to control who can cancel requests. Without this feature, anyone with edit permissions for Requests (permission to be created as part of UXPROD-1808 Closed ) will also be able to cancel.

Current thinking on design:

  • FOLIO currently only supports CRUD-based permissions
  • Cancel is not part of CRUD, so we will need the Action Based Permissions feature ( UXPROD-1828 Closed ) completed before we can implement this permission

NOTE: This was originally part of a larger permission feature ( UXPROD-236 Closed ).



 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

Comment by David Bottorff [ 02/Jul/19 ]

Chicago can wait up to 1 year for this, as it would be acceptable to rely on the edit request permission for our purposes.

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

Thanks for your comment David Bottorff. I have changed Chicago to can wait up to 1 year.

Comment by Erin Nettifee [ 09/Jul/19 ]

Duke can wait up to a year.

Comment by Erin Nettifee [ 17/Mar/21 ]

After discussion with Holly and Marc Johnson, I have removed the link that had this blocked by https://folio-org.atlassian.net/browse/UXPROD-1828 so that it can proceed with prioritization and development as appropriate.

Comment by Holly Mistlebauer [ 07/Mar/22 ]

This feature is marked DRAFT until Brooks Travis has a chance to review it for validity.

Comment by Khalilah Gambrell [ 06/Sep/22 ]

Brooks Travis  - in a nutshell, is this feature just to support a library assigning a cancel request permission AND NOT assign an Edit permission. So the user assigned the cancel request permission only would only have this action on the detail record?

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