• Attendees / Apologies
• Upcoming Availability

NA

Code Review: 

• ERM-1798 - Getting issue details... STATUS
  • integration tests reviewed:
    • does not gel with existing tests
    • will need new values and possible tests
  • refactor on tests should not block QA 
  • some testing has been done to check against the ingest process
  • transferred to Owen for QA
  • new subtask raised to track integration test tweaks: ERM-1880 - Getting issue details... STATUS
• ERM-1259 - Getting issue details... STATUS
  • some scenarios missing and not identified
  • to follow up with Adi post-call
• ERM-1853 - Getting issue details... STATUS / ERM-1854 - Getting issue details... STATUS

QA / UAT 

• No issues expected
  • ERM-1816 - Getting issue details... STATUS
  • ERM-1848 - Getting issue details... STATUS
  • ERM-1754 - Getting issue details... STATUS
  • ERM-1862 - Getting issue details... STATUS
• ERM-1628 - Getting issue details... STATUS
  • need to review for potential testing issues
  • empty accordians aren't shown anymore so circumstances for issue arising are rarely triggered

Bugfix Cycle 

• NA

• ERM-1700 - Getting issue details... STATUS
  • locally,
    • internal contacts are not linked
    • need to select agreement twice to enable linkable admin contact
    • users are not added in local build of platform-erm
  • not the same on snapshot -
    • shouldn't need to worry about it
    • may be separate bug: 
      • Owen to review 
      • would be a good place to use react query
      • if so, then should come up with a pattern first
• ERM-1661 - Getting issue details... STATUS
  • just started
  • agreements.js, eresources and platforms will take a significant time - completely
    • use sas from smart-components
    • potentially 4 days
  • other tests should be 4-5 days
• ERM-1258 - Getting issue details... STATUS
  • not seeing the reason tests are 
• ERM-1813 - Getting issue details... STATUS
  • Adding 'relatedTitles' to the expansion list doesn't make any difference.
  • Some formatting to the issue description to highlight the differences between the scenarios.
  • To try alternative approach: 
    • ti not pti
    • ti.work.titles that aren't current
    • titles shouldn't be fully rendered
• ERM-1771 - Getting issue details... STATUS / ERM-1770 - Getting issue details... STATUS
  • front-end issue (stripes-erm-components)
  • two approaches considered
  • choice is when custom properties are created, ignore everything unless value is entered
    • rather than validate dirty fields
  • will add a delete prop as default for primary properties

Sprint Backlog - Next Up

• Claudia:
  • potentially ERM-1566 - Getting issue details... STATUS
  • recent example in ERM-1859
  • may need to add similar more in other issues
    • Gill to review and liaise with Owen to raise relevant issues
• Peter:  ERM-1850 - Getting issue details... STATUS
• Ethan: 
  • Release Tasks
  • ERM-1880 - Getting issue details... STATUS Integration tests for ERM-1798
  • ERM-1799
• Adi: 
  • RTL tasks not requiring SaS/smart-components
  • Frontend Release Tasks
  • RTL tasks using SaS/smart-components
• Monireh: RTL tests

Sprint Backlog - to follow

• NA

Needs Elaboration

• ERM-1733 - Getting issue details... STATUS

Blocked

• NA

Sprint Backlog 

• ERM-1287 - Getting issue details... STATUS
  • at risk this sprint because of extra time needed for new sas related RTL tests for ERM-1661 
• ERM-1733 - Getting issue details... STATUS

Accepted 

• ERM-1844 - Getting issue details... STATUS
  • should be good to close 
  • no testrail cases to be raised

New Issues

Added to sprint

• ERM-1853 - Getting issue details... STATUS
• ERM-1854 - Getting issue details... STATUS
• ERM-1566 - Getting issue details... STATUS