Agreements (UXPROD-573)

[UXPROD-2875] Agreements Organisation management Created: 21/Jan/21  Updated: 01/Sep/21  Resolved: 01/Sep/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: Agreements

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

Issue links:
Cloners
is cloned by UXPROD-2887 Licenses Organisation management Closed
Defines
is defined by ERM-1540 Support for multiple roles per organi... Closed
is defined by ERM-1542 Make organization roles for agreement... Closed
Epic Link: Agreements
Development Team: Bienenvolk
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:
Organisations can be linked to agreements with each organisation playing a specific "role". The Vendor role is treated in a special way, preventing this being used multiple times for a single agreement and displaying it in an agreement summary.

Institutions wish to:

  • Record multiple roles per organisation
  • Be able to define their own organisation roles
  • Be able to (optionally) nominate a "primary" organisation for display in an agreement summary
  • Not be limited to the number of organisations that can be related to a specific role

In scope

  • Changes to backend/UI to support multiple roles per agreement
  • Support for an "organisation note" and "role notes"
  • Support for tenant definition of roles (i.e. able to create and label roles at a tenant level)
  • Support for marking a single "primary" organisation for display in an agreement summary

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions


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