Agreements (UXPROD-573)

[ERM-429] Display amendments in Agreement view Created: 13/Aug/19  Updated: 23/Sep/19  Resolved: 23/Sep/19

Status: Closed
Project: ERM Platform
Components: ui-agreements
Affects versions: None
Fix versions: None
Parent: Agreements

Type: Story Priority: TBD
Reporter: Owen Stephens Assignee: md331 (Inactive)
Resolution: Done Votes: 0
Labels: erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Controlling license accordion.png     PNG File Historical licenses.png    
Issue links:
Defines
defines UXPROD-1472 Manage amendments on a license/agreem... Closed
Relates
relates to ERM-463 Agreement | Add Amendment 'Conflictin... Closed
Sprint: ERM Sprint 72
Development Team: Bienenvolk
Epic Link: Agreements

 Description   

The "License information" accordion is replaced by three separate accordions:
1. Controlling license
2. Future licences
3. Historical licenses

In the "Controlling license" accordion:

1. Show the Current amendments for the agreement in the License card.

  • If the controlling license has current amendments then
  • In the license card, display a sub-heading "Current amendments"
  • Under the new heading, display a table/list of amendments where the field "Status (this agreement)"='Current'
    • Fields to display in the list are amendment Name, Status, Start date, End date and Amendment note (this agreement)
      • Note: the first four fields are from the Amendment record and the last field is from the Agreement.
  • If the controlling license has no current amendments then do not display the heading "Current amendments"

2. Show Future amendments

  • If the controlling license has current amendments then
  • Underneath the license card, display a sub-heading "Future amendments"
  • Under the new heading, display a table/list of amendments where the field "Status (this agreement)"='Future'
    • Fields to display in the list are amendment Name, Status, Start date, End date and Amendment note (this agreement)
      • Note: the first four fields are from the Amendment record and the last field is from the Agreement.
  • If the controlling license has no future amendments then do not display the heading "Future amendments"

3. Show Historical amendments

  • If the controlling license has historical amendments then
  • Underneath the license card, display a sub-heading "Historical amendments"
  • Under the new heading, display a table/list of amendments where the field "Status (this agreement)"='Historical'
    • Fields to display in the list are amendment Name, Start date, End date and Amendment note (this agreement)
      • Note: the first three fields are from the Amendment record and the last field is from the Agreement.
  • If the controlling license has no future amendments then do not display the heading "Historical amendments"

3. Show Unset amendments

  • If the controlling license has Unset amendments (i.e. amendments without any Status in this agreement) then
  • Underneath the license card, display a sub-heading "Unset amendments"
  • Under the new heading, display a table/list of amendments where the field "Status (this agreement)" is not set
    • Fields to display in the list are amendment Name, Start date, End date
  • If the controlling license has no unset amendments then do not display the heading "Unset amendments"
    Notes:
  • amendments are not shown in the preview pane when the field: "Status (this agreement)" = "Does not apply" (see ERM-428 Closed ).
  • scope of this story is for amendments related to the controlling license only

Mock-up showing the Controlling license accordion with Current, Future and Historical amendments.



 Comments   
Comment by Jag Goraya [ 26/Aug/19 ]

The MVP display option would be to only show amendments for the controlling license that have a Current agreement-license status link.

Comment by Gill Osguthorpe [ 28/Aug/19 ]

Handling of Future licenses and Historical licenses is not covered in this feature. Below is mock-up of the latter, and has been shown to users at the Sub-SIG.

If users have comments about this overall approach they will add them to this document: https://docs.google.com/document/d/1HrUzIb-vSRQNjaQ8ArsUzc3cReGdPzMdC83tMg4T3sA

Owen Stephens, in this approach, the "General notes about the agreement's license" field falls under the "Controlling license" accordion. Users have seen this and not commented, but I didn't ask whether this is acceptable or not.

Comment by Jag Goraya [ 10/Sep/19 ]

Following sprint planning and Slack conversation plan is to use the icon, as used in other places for consistency. This is variation from the attached wireframe. cc md331

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