Requests
(UXPROD-790)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P4 |
| Reporter: | Brooks Travis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | enettifee-reviewed, requests, ui-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Epic Link: | Requests | ||||||||||||
| Development Team: | Vega | ||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 1 | ||||||||||||
| PO Rank: | 0 | ||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||
| Rank: MO State (MVP June 2020): | R3 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||
| Description |
|
Current situation or problem: When cancelling a request, the modal prompts the FOLIO user to choose a cancellation reason, and to provide additional information for patrons. The list of cancellation reasons is configured in Settings > Circulation, with one value hardcoded that cannot be deleted in the UI ("Other"). Libraries can add additional cancellation reasons that work for them. Currently, whether the "Additional information for patron" field is required is hardcoded. For the value of "Other", it is required - for any values that libraries added to the tenant, it is optional. Instead of the hardcoded behavior, we'd like libraries to be able to configure if "Additional information for patron" is a required field for any/all request cancellation reasons on the tenant. In scope
Out of scope
Use case(s)
Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Erin Nettifee [ 17/Mar/21 ] |
|
Brooks, I really want the ability to make additional info optional or required for all of them - that's how the controls in fee/fines work. Is it possible to scope this that way? |
| Comment by Brooks Travis [ 17/Mar/21 ] |
|
Erin Nettifee Yes. I misunderstood your requirement. I'll make that update. |
| Comment by Erin Nettifee [ 17/Mar/21 ] |
|
great - thanks Brooks! |
| 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 Erin Nettifee [ 05/May/22 ] |
|
Stephanie Buck this is very low priority, but might be something that could be simple for Vega since I do believe it should be UI only. I picked it up as an assignee and can groom it with Vega when you get there. |