Agreements
(UXPROD-573)
|
|
| Status: | Blocked |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Agreements |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Owen Stephens | Assignee: | Owen Stephens |
| Resolution: | Unresolved | 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: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | It is already possible to link a POL to an Agreement line. If the PO/POL does not already exist, the user can open the Orders app in another browser tab and create the necessary PO/POL before making the link.
This feature is to improve the UX, but does not substantially enhance the functionality |
||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Agreements | ||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 3 | ||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 10 | ||||||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | This is ranked low because there is a reasonably clear and easy to implement work around | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (ERM Jun 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Sometimes a librarian may need to link an Agreement line to a POL, but the appropriate PO and/or POL won't already exist. This feature is to support the process of adding the PO/POL starting from the context of an Agreement, supporting an effective and efficient workflow for the user |
| Comments |
| Comment by Michael Arthur [ 30/May/19 ] |
|
Until we can see workflow that shows how the PO/POL will be generated starting in a Agreement (or until i learn more about why this would be done) i am not able to rank it. |
| Comment by Jag Goraya [ 18/Jun/19 ] |
|
From Washington discussions:
So, the POL needs to link to the agreement line or instance or container. |
| Comment by Ann-Marie Breaux (Inactive) [ 18/Jun/19 ] |
|
Jag Goraya Ian Ibbotson (Use this one) Owen Stephens We need to be sure the approach for this story is parallel to the Inventory solution provided by
|
| Comment by Ann-Marie Breaux (Inactive) [ 18/Jun/19 ] |
|
Jag Goraya Ian Ibbotson (Use this one) Owen Stephens Also linked the various UIIN, UX, UIOR stories that cover linking between various Inventory record types and POLs; would be great if the linking/UI for this story is parallel with the Inventory solution |
| Comment by Jag Goraya [ 15/Oct/19 ] |
|
Setting to Blocked pending completion of
|