Agreements (UXPROD-573)

[UXPROD-1157] Link resources in agreements (agreement lines) to Purchase Orders / Purchase Order Lines Created: 27/Sep/18  Updated: 16/Sep/20  Resolved: 16/Jul/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Agreements

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: erm, q2-2019-spillover, split, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-239 Link existing Purchase Order Line (PO... Closed
is defined by ERM-240 Display Purchase Order Line (POL) inf... Closed
is defined by ERM-242 Display Purchase Order Line (POL) lin... Closed
Gantt End to Start
has to be done before UXPROD-1753 Create and link PO/POL from Agreement... Blocked
Relates
relates to UIOR-320 Add configuration to plugin-find-po-l... Closed
Requires
requires UINV-7 Add invoice line based on POL Closed
requires UINV-24 Search and select POL plugin Closed
Epic Link: Agreements
Front End Estimate: Large < 10 days
Back End Estimate: Medium < 5 days
Development Team: Bienenvolk
PO Rank: 90
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R1
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

To Split: Will need splitting across Q1 2019 and Q2 2019 releases.

For each agreement line (a package or title within an agreement), support adding a purchase order line (POL) to an existing or new purchase order.

Where the agreement line is already attached to a POL display that information.



 Comments   
Comment by Jag Goraya [ 16/Jul/19 ]

Owen Stephens are you happy that, as of Sprint 67, this feature is now delivered, and that it can be Closed?

wrt to incomplete related tasks -

  • should sub-task UXPROD-1679 Open sit under UXPROD-1753 Blocked ?
  • can we close UIER-16 as Won't Do now (also, as it's in a legacy project)
Comment by Owen Stephens [ 16/Jul/19 ]

Jag Goraya
> should sub-task UXPROD-1679 Open sit under UXPROD-1753 Blocked ?
Yes [DONE]

> can we close UIER-16 as Won't Do now (also, as it's in a legacy project)
It's not made redundant by completion of UXPROD-1157 Closed . I see it as potentially part of UXPROD-1467 Closed if we decide it is required for that (discussion so far suggests it might be)

Generated at Fri Feb 09 00:13:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.