QA / UAT: all in good place to test 

• ERM-685 - Getting issue details... STATUS  /  ERM-690 - Getting issue details... STATUS

Code Review

• NA

In Progress 

• ERM-689 - Getting issue details... STATUS
  • code should work, but can't properly test extended export
  • query about easier way to get active package data
  • Ethan has a sample package json that should make that possible, if an agreement is created (which would need to done in the UI)
  • Peter to update (add or extend) dev script in mod-agreements to include package and agreement
• ERM-700 - Getting issue details... STATUS  /  ERM-702 - Getting issue details... STATUS
  • json seems to be appending names with zero characters
  • otherwise going well
  • question remains about where this is hosted
  • can be run outside of FOLIO (as an isolated GBV served script) for this iteration, but will need to be integrated with the platform
    • driver is displaying error messages in usage context
    • raises questions about cross-app logging
    • impacts licenses and subscriptionAgreements
    • to be raised with Tech Council members on Thu 27 Feb
    • agreements model is not currently expected to change to have an extensible identifier, but to use a reference instead (based on name, though this is brittle)
    • testing to be done by Felix and/or Annika
    • Ian Ibbotson (Use this one) to add acceptance criteria / statement
• Modal:  ERM-723 - Getting issue details... STATUS  
• Callout:  ERM-724 - Getting issue details... STATUS  /  ERM-725 - Getting issue details... STATUS  /  ERM-727 - Getting issue details... STATUS
  • functionality is now in stripes-core, so no need to take to the stripes team on Thursday
  • easy to pick up while waiting for laser work to 
• ERM-668 - Getting issue details... STATUS  /  ERM-684 - Getting issue details... STATUS
  • starting still expecting to QA this sprint
• ERM-713 - Getting issue details... STATUS  /  ERM-712 - Getting issue details... STATUS
  • PR just raised for frontend
  • backend not started yet
  • for backend: it is sufficient to output everything and leave it blank if no data (more efficient than only showing populated fields)
  • frontend need to know what errors might be sent back to report in UI
    • always return CSV whether or not empty
    • log backend errors in console

Raised / brought into sprint: 

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

ERM-495 - Getting issue details... STATUS