QA / UAT

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

In Progress 

• ERM-454 - Getting issue details... STATUS  
  • Moved to code review, and merged
  • "there's amendments.js but this wasn't working before my changes"
    • no issue is logged for that
    • tests are there but not working
    • tests don't run as part of PR process, need to be run locally
  • also, functionality to add documents not working
    • fixed locally
  • TODO: open new branches and Jira issues for both
• ERM-434 - Getting issue details... STATUS  
  • merged, awaiting backend
• ERM-644 - Getting issue details... STATUS
  • about to enter code review
• ERM-654 - Getting issue details... STATUS  /  ERM-655 - Getting issue details... STATUS
• UXPROD-2081 - Getting issue details... STATUS
  • Backend: fields added
  • UI
    • front end designs: to be defined / written
    • also to combine coverage data
  • Rules
    • expecting to make progress today
• ERM-642 - Getting issue details... STATUS
  • package contents element complete
  • moving on to lkb info/error logs

Raised / brought into sprint: 

• ERM-654 - Getting issue details... STATUS  /  ERM-655 - Getting issue details... STATUS

Also:

• ERM-550 - Getting issue details... STATUS
  • cannot consistently reproduce across browsers (possible that Charlotte's original issue has been resolved, though that may just be Mac's disappearing scrollbar)
  • appears to be Win10 only, possibly Chrome only
  • May be related to the scrollbar work done by John Coburn
  • md331 (Deactivated)  to transfer issue to STCOM

• ERM-506 - Getting issue details... STATUS  
  • outside of FOLIO scope
  • no capacity to have explored so far
  • meaningful log interrogation is still likely a priority
  • this doesn't need to be the solution and streaming then being a dependency
  • streaming is likely the easiest option to implement
  • logs is the most likely use case to test a streaming implementation (as well as eresource entitlement)
  • OS to consider priority for scheduling investigation of this: ERM-633 still takes precedence.
• ERM-510 - Getting issue details... STATUS  
  • Q: how to identify a record?
  • See notes on ERM Sprints 79-80. Owen to followup with Steve.

WolfCon aims: 

1. understand how people use the functionality in actual practice (concrete use cases) - existing and gaps
2. have cross-app integration conversations, including how to practically take those forward for delivery

Wolfcon schedule: https://wolfcon2020a.sched.com/