Requests (UXPROD-790)

[UXPROD-897] Requests: re-setting an in-process request to "Open - not yet filled" Created: 12/Jun/18  Updated: 23/Feb/23

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: Unassigned
Resolution: Unresolved Votes: 0
Labels: requests, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-1087 Change from other "Open" Request Stat... Open
is defined by UIREQ-577 Add 'Move Request' option to Action m... Open
is defined by UIREQ-584 Add 'Reset to Open - not yet filled' ... Open
Issue split
split to UXPROD-4089 Add Request Notice Trigger for "Item ... Draft
Potential Workaround: Cancel and re-place the request.
Epic Link: Requests
Analysis Estimate: Medium < 5 days
Analysis Estimator: Tania Fersenheim
Front End Estimate: Medium < 5 days
Front End Estimator: Tania Fersenheim
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Tania Fersenheim
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 75
PO Ranking Note: 2021-02-25 - BT: Updating PO rank to more closely match calculated total rank, but bumping up a point to avoid two features with the same rank.
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): R2
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Mainz (Full TBD): R3
Rank: MI State-Lib of MI (Sum 2021): R4
Rank: MO State (MVP June 2020): R2
Rank: St. Michael's College (Sum 2021): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: Implement the ability to reset an open request to "Open - not yet filled" request status, including:

  • Staff slips and notices to the patron
  • How, when and by whom a request can be reset CB: Moved from UXPROD-236 Closed . This will require an action-based permission which is out of scope for this feature We're going to remove the need to separately permission this action. Will only require update request permission. (per conversations with RA SIG on 2020-02-22 -BT)
  • What happens to the item associated with the reset request


 Comments   
Comment by Tania Fersenheim [ 12/Jun/18 ]

Matt Connolly and Marc Johnson - let's talk about how to estimate front end and back end

Comment by Tania Fersenheim [ 27/Jun/18 ]

Matt Connolly & Marc Johnson - I applied back and front end estimates to this - could you each do a sanity check on the estimates and let me know if you want to talk over the issue

Comment by Marc Johnson [ 29/Jun/18 ]

Tania Fersenheim Looks ok to me. I'm curious, under what circumstances would we want to do this, because it has got stuck in the request fulfilment process somehow?

Comment by Tania Fersenheim [ 29/Jun/18 ]

Marc Johnson - Sort of. Either the item goes AWOL (not super common but not unheard of) or a decision is made that an item needs to have something else done with it. E.g. checking it out to a different person, routed temporarily to repair, etc, but the original request still needs to be filled and still needs to retain its position in the queue.
We envision this function as something that can be manually done by staff and will eventually be part of a multi-step-behind-the-scenes process that FOLIO will execute when a staff person does an override of a checkout block.

Comment by Anya [ 29/Mar/19 ]

Comment from March meeting : if it is just a status wording issues - it is not needed

Comment by Marie Widigson [ 22/Feb/21 ]

Changing our ranking to R2 for this feature since it's needed for UIREQ-577 Open

Comment by Brooks Travis [ 25/Feb/21 ]

Marc Johnson Holly Mistlebauer I've updated this ticket to remove the requirement for an action-based permission, per conversations with the RA SIG on 2021-02-22. I'm going to remove UXPROD-1828 Closed as a blocker. With that in mind, can we take another look at the estimates on this? I'll work on updating the stories for UI and backend.

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 Brooks Travis [ 07/Mar/22 ]

Stephanie Buck julie.bickle Might be worth reviewing this with Vega Devs, or at least having them take a look at it so they can ask questions. It's not super high-priority. Including you, Julie, because of the notice trigger story.

Comment by Stephanie Buck [ 09/Mar/22 ]

Brooks Travis, julie.bickle will be joining Vega's Friday refinement sessions. They are every other week at 10am ET. If you'd like to coordinate with Julie when to review with Vega, just let me know what date works for you.

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