Code Review: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-510

  • works locally now, displaying JSON info as expected
  • progressed to Code Review
  • Owen to create separate story to add the info into UI

In Progress 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-950

  • App is done
  • Tests begun
  • Weird issue re filters: 
    • not showing up in URL
    • Tests seem to block test writing
  • Standalone works
  • Running without ui-agreements runs fine, introducing it causes the filters to not display
  • Two filters with different names = shouldn't be an issue
  • Filters call the plugins, which each call mod-agreements
    • potentially caching some ui-agreements
  • Set up as with other 
  • datakey is being passed in, though needs to be unique
    • may be the same that's being passed in on both filters. 
  • needs a separate endpoint which will be used by ERM-951

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-951

  • depends on backend of ERM-950 being merged
  • however there is a PR build failrure because of 
  • JSON structure is not confirmed to be being returned
  • has some dummy data being passed to MCL resembling ERM-953 wireframes
  • frontend work required: 
    • need callback properties in MCL 
    • awaiting shape from ERM-959: added sample during call
  • assume it is data.endpoint
  • will need a STCOM PR 
    • probably ready today
  • will continue to work off Ethan's branch locally

Raised / to bring into sprint: NA

Raised: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-976

   
  • raised as mitigation for ERM-974 and ERM-975
  • brings into line with similar user feedback behaviour introduced for PO lines
  • not required for Goldenrod
  • should be available for Ready to Progress 

NA