Agreements
(UXPROD-573)
|
|
| 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: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Sprint: | ERM Sprint 72 | ||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||
| Epic Link: | Agreements | ||||||||||||||||
| Description |
|
The "License information" accordion is replaced by three separate accordions: In the "Controlling license" accordion: 1. Show the Current amendments for the agreement in the License card.
2. Show Future amendments
3. Show Historical amendments
3. Show Unset amendments
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 |