2021-03-03 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Mar 03, 2021

Meeting Details

Date

    

Time

10:30am ET, 3:30pm UK, 4:30pm Germany

Location

Video Call in

Previously2021-02-24 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Adi

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions



Previous Actions




WIP Update 

Release Candidates

Code Review: 

  • NA

QA / UAT 

No impediment

For Release

  • NA

Items at Risk / Spillover

In Progress

  • ERM-1544 - Getting issue details... STATUS
    • refactored agreement filters 
    • showing all filters and new tags filter working
    • old tags not working in switch to functional structure
    • currently debugging
  • ERM-1579 - Getting issue details... STATUS
    • tokens will be done on front end
    • form UI is causing problems
    • mockup revisions also pending - due later today
  • ERM-1581 - Getting issue details... STATUS
    • basically done
    • needs to be extended to amendments as well
    • due for code review today

Sprint Backlog

  • ERM-1564 - Getting issue details... STATUS
  • ERM-1580 - Getting issue details... STATUS
  • ERM-1547 - Getting issue details... STATUS
    • reset use state may be effective
    • form object should yield the object reference needed 

Needs Elaboration

  • NA

Closed

  • NA


<10 minsAOB

New Issues

Added to sprint

Not added to sprint

  • NA 

Organisation Roles

Issues:  ERM-1540 - Getting issue details... STATUS / ERM-1541 - Getting issue details... STATUS / ERM-1542 - Getting issue details... STATUS / ERM-1543 - Getting issue details... STATUS

  • REQ: change current setup to support
    • multiple organisations with multiple roles for an agreement or license
    • one primary organisation per license or agreement (pattern as per contact address)
  • UNKNOWNS:
    • impact on filtering by org(s)/role(s)
    • migration
  • TASK TBC: new domain class on SubscriptionAgreement to support role-note pairs
  • Remove exclusive vendor restriction
  • PLAN:
    • Ethan: determine data model and class changes (solicit feedback from Ian/Steve)
    • Owen: add migration scenarios to issue
    • Claudia: review updated information and define work breakdown required