Page Comparison

• Attendees / Apologies
• Upcoming Availability

Release Candidates

Code Review: 

QA / UAT 

For Release

Items at Risk / Spillover

In Progress

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1537

  • getting errors with no clear origin
  • no example test for this kind of complex view component found
  • Tests to be deferred - Claudia to raise issue for Adi to review on return
  • Minor correction to be resubmitted for code review

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1544

  • tag values are not showing in search & filter
  • url is showing object.object rather than a value - 
    • expected behaviour can be compared from licenses
  • can use console to debug and inspect object model 

Sprint Backlog

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1559

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1560

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1564

  • There should be a cleanup task in addition to saving on clone
  • This may already exist as ermHousekeepingService, which calls a number of collation subservices, such as coverageService.coalesceCoverageStatements and SubscriptionAgreementCleanupService
    • These do not address the underlying issue
  • New cleanup trigger subtask created: 

    Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1565

  • Should be able to address with existing methods
  • Fix on cloning needs more investigation (function doClone)
    • this doesn't clone the periods though (and therefore the period status also)
  • Will need to tunnel through with debug info to get to the bottom of this one.
  • Owen to add issue to support user option to clone periods

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1561

  • moved to In Progress
  • run into some stripes-connect issues, but seem to have resolved these, and this is preference to use go forward
  • got a lightweight table component up and running
  • some minor styling to resolve 
  • Demo given of current dashboard WIP 
  • TODO: widget weighting

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1562

Needs Elaboration

New Issues

Added to sprint

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-1564