Agreements (UXPROD-573)

[UXPROD-2815] Document and Rationalise permissions and related behaviour in Agreements Created: 12/Nov/20  Updated: 15/Mar/21  Resolved: 15/Mar/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Agreements

Type: New Feature Priority: TBD
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: agreements, erm
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-2816 Document and Rationalise permissions ... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
UXPROD-2976 Create example permission sets and us... Sub-task Closed Owen Stephens  
UXPROD-2979 Add Agreements permissions to draft d... Sub-task Closed Owen Stephens  
UXPROD-2982 Add Agreements permissions to permiss... Sub-task Closed Owen Stephens  
UXPROD-2983 Add Local KB Admin permissions to per... Sub-task Closed Owen Stephens  
UXPROD-2984 Add ERM Comparisons permissions to pe... Sub-task Closed Owen Stephens  
Epic Link: Agreements
Development Team: Bienenvolk
PO Rank: 30
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R1
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:
Permissions in the agreements app are defined at a relatively granular level, which leads to situations where users have combinations of permissions that don't make sense.

Additionally in cases where users don't have the correct permissions they may see inconsistent behaviour (e.g. sometimes an error, sometimes data is just not displayed, sometimes data is partially displayed)

In scope

  • Documenting current situation with regards permissions and behaviour when user doesn't have permissions to view some of the data needed for a screen
  • Ensuring all current permissions within Agreements make sense and work well together
  • Documenting required behaviour where the user doesn't have permission in another app (e.g. Users, Organisations)
  • Ensuring that where a user does not have permission to view specific data, the app will handle this with a set of consistent behaviours


 Comments   
Comment by Owen Stephens [ 06/Jan/21 ]

ERM Subgroup worked to document common roles for ERM in libraries, these are documented here
https://docs.google.com/document/d/1HLk3QlIkcCoOz3mPU2ZvODqtxVzgDuNSYrhNeegE9wY/edit#heading=h.yts89j58ygsa

Comment by Owen Stephens [ 06/Jan/21 ]

It maybe helpful to refer to this spreadsheet (created by Wayne at ID) of all the UI permissions across apps in Goldenrod and Honeysuckle releases https://docs.google.com/spreadsheets/d/1siMHfUyU1bYRi0cprhBj8J7iNVkP-tox7H3VRhHXuPg/edit?usp=sharing

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