Agreements
(UXPROD-573)
|
|
| Status: | Closed |
| Project: | ERM Platform |
| Components: | mod-agreements, ui-agreements |
| Affects versions: | None |
| Fix versions: | None | Parent: | Agreements |
| Type: | Story | Priority: | P3 |
| Reporter: | Owen Stephens | Assignee: | steve.osguthorpe |
| Resolution: | Done | Votes: | 0 |
| Labels: | agreements, erm | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original estimate: | Not Specified |
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Sub-tasks: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | ERM Sprint 64, ERM Sprint 67 | ||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 7 | ||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Agreements | ||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Value for user:
Examples: Roles and restrictions:
Workflow / UI expectations: Business rules & constraints: See also https://folio-org.atlassian.net/browse/ERM-240 for mockups |
| Comments |
| Comment by Jag Goraya [ 20/Jun/19 ] |
|
Aditya matukumalli md331 We previously required
|
| Comment by Aditya matukumalli [ 21/Jun/19 ] |
|
Jag Goraya I believe it should be sufficient for us if
|
| Comment by md331 (Inactive) [ 21/Jun/19 ] |
|
Jag Goraya the only thing I wonder about is how the order lines and invoices relate to one another and where the information we want is. In our current code, when listing PO Lines, I see we have columns for name, type, cost type, gross, net, tax and a link the PO Line. Only name and the PO Line link are currently even being attempted to render, so we don't appear to have any clue where the remaining fields should come from. I wonder whether they might actually come from the invoice rather than the purchase order? I couldn't find anything specifically about those fields in the POLine API. |
| Comment by md331 (Inactive) [ 21/Jun/19 ] |
|
But if we're only concerned about linking and not necessarily showing all the relevant data we have columns for, then yes,
|
| Comment by Owen Stephens [ 21/Jun/19 ] |
|
md331 Aditya matukumalli Jag Goraya we have https://folio-org.atlassian.net/browse/ERM-240 which is about the display of the POL data. As md331 mentions, display of information from Invoices is also likely to be required but I've been waiting for the POL -> Invoice work to complete to start to understand what is needed here |
| Comment by Jag Goraya [ 24/Jun/19 ] |
md331 Aditya matukumalli: These are no longer needed for this story implementation (we'll revisit with a later feature). The fields in
|
| Comment by steve.osguthorpe [ 01/Jul/19 ] |
| Comment by md331 (Inactive) [ 01/Jul/19 ] |
|
Fields available for an order line when it's selected are likely the same as these. |
| Comment by Jag Goraya [ 03/Jul/19 ] |
|
From Slack thread:
|
| Comment by Jag Goraya [ 04/Jul/19 ] |
|
Linked
|