UX improvements for Agreements up to Q3 2020
(UXPROD-1669)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UX improvements for Agreements up to Q3 2020 |
| Type: | Sub-task | Priority: | TBD |
| Reporter: | Gill Osguthorpe | Assignee: | Gill Osguthorpe |
| Resolution: | Done | Votes: | 0 |
| Labels: | agreements, erm, ux-consistency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Development Team: | Bienenvolk | ||||||||
| Description |
|
The small agreement icon needs to be added as follows: 1. In the Agreement Preview pane to the left of the Agreement name in the header, as show in the mockup. 2. In the search and sort results list, to the left of the Agreement name, as shown in the mockup.
3. In the Edit Agreement pane and New Agreement pane to the left of the Agreement name in the header, as show in the mockup. |
| Comments |
| Comment by Owen Stephens [ 08/Jul/19 ] |
|
Gill Osguthorpe - I think (1) and (3) are already done, but (2) is not. Do you agree? If it's just (2) that needs doing - can you create a separate story for that? Thanks |
| Comment by Gill Osguthorpe [ 22/Jul/19 ] |
|
Owen Stephens Yes 1 and 3 are complete. I'll create a separate story for 2, if you agree it makes sense as a feature right now. If there are plans for tenants to be able to manage their own vocab for "agreement status" will we need to give user control over which values will show as "inactive". For now shall we go with hardcoding for "Rejected" and "Cancelled"? |
| Comment by Gill Osguthorpe [ 30/Sep/19 ] |
|
Hi Owen Stephens. Shall I go ahead with the story for (2), for agreements which are "Rejected" or "Closed"? |
| Comment by Owen Stephens [ 30/Sep/19 ] |
|
Hi Gill Osguthorpe once
|
| Comment by Gill Osguthorpe [ 10/Oct/19 ] |
|
Story
|