Receiving functionality that FOLIO needs to stay competitive
(UXPROD-3438)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Lotus (R1 2022) | Parent: | Receiving functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Done | Votes: | 0 |
| Labels: | acquisitions | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||
| Epic Link: | Receiving functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Receiving functionality can appear complex to users as multiple data points control separate workflow and are broken up between records that appear in the orders app and records that appear in the receiving app. In scope
Out of scope Managing pieces based on publication patterns Links to additional information See wiki page https://folio-org.atlassian.net/wiki/x/wAZU.
|
| Comments |
| Comment by Dennis Bridges [ 18/Apr/22 ] |
|
Testing successful in bugfest-lotus |