Requests
(UXPROD-790)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Tania Fersenheim |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | requests, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Epic Link: | Requests | ||||||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||||||
| Analysis Estimator: | Darcy Branchini | ||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||
| Front End Estimator: | Darcy Branchini | ||||||||||||||||||||||||
| Back End Estimate: | Very Small (VS) < 1 day | ||||||||||||||||||||||||
| Back End Estimator: | Darcy Branchini | ||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Based on item status only and assumes an immediate modal notification "in situ". | ||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||
| Description |
|
Purpose: To define and implement request-related alerts that appear during Check In, including:
|
| Comments |
| Comment by Cate Boerema (Inactive) [ 04/Apr/18 ] |
|
Tania Fersenheim, do you think this feature should be assigned to you? |
| Comment by Cate Boerema (Inactive) [ 05/Apr/18 ] |
|
Tania Fersenheim, I am just going to go ahead and assign this to you. Please let me know if that seems wrong. |
| Comment by Tania Fersenheim [ 11/Apr/18 ] |
|
Cate Boerema - apologies. Yes this should definitely be assigned to me! |
| Comment by Emma Boettcher [ 13/Apr/18 ] |
|
Tania Fersenheim Cate Boerema I'm also watching this one because it seems similar to
|
| Comment by Tania Fersenheim [ 13/Apr/18 ] |
|
I need to either edit this issue to include checkout and renewal, or create new UXPROD issues for checkout and renewal. Any opinions on which route I should take? |
| Comment by Cate Boerema (Inactive) [ 16/Apr/18 ] |
|
Was this originally just for Check in? If so, I would create separate UXPRODs for Check out and Renewal. I say that only because there are some estimates on this feature and, if you dramatically change the scope, they will no longer be valid. Thanks! Cate |
| Comment by Cate Boerema (Inactive) [ 27/Sep/18 ] |
|
Tania Fersenheim, this feature is kind of vague and, in theory, could cover many different triggers (e.g. item needs to go on hold shelf at this service point, item needs to go in transit to another service point for a hold, item needs to be delivered). Given that, I feel like the feature is too broad and has too many dependencies to neatly fit into a quarter. I'm thinking it might make sense to just include any alerts that need to display at the time of check-in in the features that drive the generation of the alert. For example, Fulfill pickup request (
|
| Comment by Tania Fersenheim [ 03/Oct/18 ] |
|
Alert requirements have been folded into each feature - see
|