2019-04-17 ERM Delivery Weekly Update

Discussion items

TimeItemNotesAction Items
<5 minsIntroductions
  •  
30 minsDemos
  • In Development
  • In Code Review
  • In QA / Accepted
  •  
10 minsSprint Completion
  • Merge Cutoff
    • Back-end:
      • Thursday 2pm UK
      • Monday 2pm US 
    • Release after sprint turnover on Tuesday morning
  • Items at Risk / Spillover
    • ERM-49 - Getting issue details... STATUS
    • ERM-92 - Getting issue details... STATUS
    • ERM-162 - Getting issue details... STATUS
    • ERM-163 - Getting issue details... STATUS
  •  
10 minsUpcoming SprintSee ERM Next Sprint Candidates list in https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=89&view=planning.nodetail
5+AOB
  • Aditya matukumallito set up new task in jira/ERM to begin unit tests for stripes-erm-components 


Sprint WIP Demos

Delivery Board: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=89

FeatureIssueWhoNotes / TODO

UXPROD-1302 - Getting issue details... STATUS

ERM-173 - Getting issue details... STATUS  /  ERM-174 - Getting issue details... STATUS

UXPROD-775 handles system-wide tag deletion

UXPROD-1520 - Getting issue details... STATUS

ERM-162 - Getting issue details... STATUS  / ERM-163 - Getting issue details... STATUS


UXPROD-1559 - Getting issue details... STATUS


ERM-79 - Getting issue details... STATUS

Nested arrays cannot be sorted currently. Similar issue with coverage statements. That's being done in line 105 of entitlement.groovy, so that may be reusable code model.


ERM-92 - Getting issue details... STATUS

Generator changes made. Held up with testing strategy, so no PR made yet. 


ERM-49 - Getting issue details... STATUS

Kurt has had discussion with Wayne Schreider. Moving away from ansible roles, towards a front-end module to provision those permissions. Details in Jira.

(Preference is to use this for all bootstrapping.) Makes sense to do with permission sets. 


ERM-139 - Getting issue details... STATUS

Aim to wrap up next couple of days, pending input from JohnC. Problem being tackled is to address deeply nested paths (eg, /license/record/id/edit/amendment ). 

SearchAndSortQuery gives more direct control over how results are handled. Works well for some applications, such as licenses, where it handles data routing better.