Versions Compared

Old Version 5

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version Current

changes.mady.by.user Jag Goraya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date

 

Time

09:30am ET, 2:30pm UK, 3:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers


Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •   
5 minsPrevious Actions
  • NA


20 mins

WIP Updates
  • Pending: 
    • what's dependent?
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-376
         - should be more straightforward than originally anticipated, as resource export is already in place 
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-546
        • re-written story, and code update drafted
        • Owen to pickup 
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-356
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-463
         - pending Gill's return
  • In Progress: what's left to do?
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-459
      • agreement name testable
      • stuck on what next for mocking clone result
        • other than test requests include additional agreement sections
      • best option agreed is to then get it in front of PO for testing
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-457
       / 
      Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-394
       / 
      Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-396
      • writing tests at the moment
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-392
       and 
      Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-393
      • reset database
      • grails documentation may be misleading
      • PO has done some testing in current state - behaviour is false
      • fix is to ensure that isDirty is not be used for new titles (could be identified by null ids)
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-549
      • working against work-in-progress ERM-508
      • writing tests in BigTest to remove reliance on Orders - new territory, so may take a bit longer 
  • For Review: 
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-508
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-544
  • For Release
  •   

10 mins

New Issues
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-544
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-550
    • could just be Mac behaviour



<10 minsAOB
  • Test data:
    • maybe get linked from wiki or in Jira issues
    • reusable sample agreement(s) to cover test scenarios
  • Claudia: 
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-548
  • Ethan: 
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-436
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-545