Invoicing functionality that FOLIO needs to stay competitive
(UXPROD-3439)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Invoicing functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | IC_review, SolutionArchitecture, acquisitions, galileo, lc-priority4, loc, requires-discussion | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Sunflower (R3 2024) | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Invoicing functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Dennis Bridges | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 70% | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Dennis Bridges | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 70% | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Confidence factor will increase after orders history has been implemented. Could be less than expected if a lot of that work can be reused. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 132 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Not enough metadata is captured regarding record activity. Some records (eg. order) are edited frequently and often by different users OR integrations. Currently it is only possible to see who last edited the invoice and who created it. This can make it difficult to troubleshoot invoices over time and uncover why something is not as expected. In scope Follow implementation approach laid out for orders in
Out of scope Use case(s)
Proposed solution/stories Use the same approach as
Links to additional info Order change log analysis in wiki at https://folio-org.atlassian.net/wiki/x/agVU |