Release Candidates

Code Review: 

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-948

  • changes have been approved
  • CI has failed, so not mergeable
  • Claudia will need the credentials to read on the build ... details are in the PR / CI Jenkins merge notes on jenkins-aws.indexdata.com. 
  • Once complete, can be merged. 

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

QA / UAT: NA

Bugix: 

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-841

  • will be released to bugfix environment at 10am EST

Items at Risk / Spillover

Blocked

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-888

  • New API has been released, so no longer blocked
  • Revisit this after the in-train comparison 
  • Expect to not begin until next week.

In Progress

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-510

  • local dev environment problem is fixed
  • to investigate the GSON file. 

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-950

  • basic functionality broadly working
  • secondary calls nearly working
  • some known issues to iron out before ready for code review / QA
  • Some future use cases to consider in terms of component structure

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-954

  • icons to be dealt with in the future
  • other than that, this is probably 

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-

• 953

  • keeping open, as needs to be revisited to allow for explaining data overlap 
  • Some tweaks rather than substantial reworking to improve contextual information for report users
  • Possibly adjustment to existing columns / additional columns 
  • Grouping / merged row presentation notes
    • Sorting would be inappropriate
    • Filtering is viable
    • Vertical centre alignment is not possible (eg, Platform) with the merged rows
    • Columns that don't vary should not be put in between columns that do vary (nested group issue)
    • targeted css is being used in split cells, so could be elaborated for colour coding 
  • Overlap information may change the shape
    • overlap field values from
      • Full - share a PCI
      • Partial - ...
      • None - don't share a title instance
    • needed because  and  may mean different things in different contexts
    • question about where and when the Overlap value is calculated - in backend seems preferable

Sprint Backlog

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-951

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-952

Needs Elaboration: NA

Raised

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-960

   / 

  Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-961

   /

  Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-

• 963

   
  • straightforward to replicate
  • not so straightforward to solve
  • points to undefined array element 

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-

• 962

•  - cannot reproduce

• Jira Legacy
  server System

• JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-964

Additional

Persisted accordian behaviour

• is doable
• similar approach to panes could be taken 

Last regular ERM call with md331 (Deactivated)

• much appreciation all round for his support, contribution and commitment on the team.