Release Candidates

Code Review: 

• ERM-547 - Getting issue details... STATUS
  • Steve to review
• ERM-793 - Getting issue details... STATUS  /  ERM-794 - Getting issue details... STATUS  /  ERM-795 - Getting issue details... STATUS
  • Steve to review backend before Mark can review 
  • backend review is a big job
• ERM-805 - Getting issue details... STATUS
  • Adi reviewing

QA / UAT: 

• ERM-746 - Getting issue details... STATUS
  • Ready for Release
• ERM-807 - Getting issue details... STATUS  /  ERM-800 - Getting issue details... STATUS  /  ERM-814 - Getting issue details... STATUS  /  ERM-835 - Getting issue details... STATUS
  • all pending QA

Items at Risk / Spillover

In Progress

• ERM-694 - Getting issue details... STATUS
  • done, but wrapped in with  ERM-779
  • will push for review with ERM-779
• ERM-748 - Getting issue details... STATUS  /  ERM-777 - Getting issue details... STATUS
  • using override method rather than events
  • less reusable, but best option
• ERM-779 - Getting issue details... STATUS
  • FE mostly done barring final checks
  • can test migrations if put within a changeset, rather than dropping table.
• ERM-827 - Getting issue details... STATUS
  • under consideration: what to display when no alternative names are presented
  • solution as applied by Claudia to stand (ie, show nothing)

Open / Sprint Backlog

• ERM-834 - Getting issue details... STATUS
  • lower priority than other sprint work
  • not as simple as previously considered
  • to do with ERM-836
• ERM-788 - Getting issue details... STATUS
  • needs some dedicated time on Thursday to ready for next sprint
• ERM-828 - Getting issue details... STATUS
  • very quick to implement when licenses model is done (ERM-827)

Needs Elaboration

• ERM-829 - Getting issue details... STATUS
  • Question is around opening up custom properties as a generic solution
  • Progress discussion with subgroup over last two weeks
  • Not sure that we don't need custom properties
  • But there are some more specific requirements emerging (as well as if not instead of re-applying custom properties)
  • Reviewing feedback and the many various touchpoints to work out what to do next
  • Notes may not be a good solution either
  • Challenge is that any first solution here may be wrongfully re-purposed for workarounds, which will have downstream data quality issues
  • Not going to to progress custom properties in next sprint
  • Need to avoid putting things on the 'source of truth' kb record

Raised

• ERM-835 - Getting issue details... STATUS  - see above
• ERM-836 - Getting issue details... STATUS  - Peter to pick up with ERM-834

Additional

• ERM-550 - Getting issue details... STATUS  
  • could it be basket overflowing from the render area triggering a size re-calculation?
  • Owen seems to be able to reproduce on Catalina at 100%

Should not combine errata and custom properties

Ready to Progress reviewed/triaged

• API change for LAS:eR - Ethan to progress, along with ERM-831 and ERM-832