Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Orchid (R1 2023) | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Done | Votes: | 0 |
| Labels: | acq-morningglory-candidate, acquisitions, kafka | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 80% | ||||||||||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 50% | ||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | We need to think about splitting stories based on Moving item vs moving Holdings. | ||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||
| PO Rank: | 55 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||
| Solution Architect: | Raman Auramau | ||||||||||||||||||||||||||||||||
| Description |
Overview:Receiving updates in
Use cases:See wiki page: https://folio-org.atlassian.net/wiki/x/zQ1U Approach |
| Comments |
| Comment by Dennis Bridges [ 25/Oct/22 ] |
|
This was split into UXPROD-3879 to separate the synchronization of updates flowing from receiving to inventory and the updates flowing from inventory to receiving. This feature will represent updates flowing from receiving to inventory. |
| Comment by Dennis Bridges [ 28/Mar/23 ] |
|
All stories resolved for release in Orchid |