UX improvements for Agreements up to Q3 2020 (UXPROD-1669)

[UXPROD-1780] Display the small Agreement icon Created: 18/Jun/19  Updated: 10/Mar/20  Resolved: 10/Mar/20

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: PNG File agreement icon grey x14.png     PNG File image-2019-06-18-10-14-16-840.png     PNG File image-2019-06-18-11-53-54-574.png     PNG File image-2019-06-18-11-57-14-085.png    
Issue links:
Cloners
is cloned by ERM-484 Indicate "Closed" agreements in Agree... Closed
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.
See example in Users app: https://folio-testing.aws.indexdata.com/users/view/a23eac4b-955e-451c-b4ff-6ec2f5e63e23

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.
See "new user" in Users app for an example.



 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 ERM-465 Closed is implemented there should only be "Closed" as a closed status - I think you can go ahead with a story for (2) on this basis.

Comment by Gill Osguthorpe [ 10/Oct/19 ]

Story ERM-484 Closed has been created for number (2).

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