ERM Sprint 69

Owned by Jag Goraya
Last updated: Jul 31, 2019 by Claudia Malzer

Sprint Goal

  • UXPROD-1755 Present terms in discovery system: required for Chalmers go-live
  • Unblock upcoming backlog dependencies (limited support in Sprints 70-71)

Sprint Schedule

  • Sprint: 69
  • Quarter: 2019 Q3
  • Start Monday 29 Jul, 2pm UK
  • Finish Friday 9 Aug, 1pm UK
  • Retrospective


Sprint Capacity

Team Availability: Schedule

Notes / Exceptions:

Lead Roles:

QA Environment: folio-testing

Navigation

 Sprint Planning Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions

Sprint Planning  

(error) - not in sprint

(tick) or @ - in sprint 

 

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-1669 - Getting issue details... STATUS

ERM-306 - Getting issue details... STATUS

Gill Osguthorpe

Carried over for QA

ERM-274 - Getting issue details... STATUS

Kurt Nordstrom

BE: 6h FE: 0h

TODO: implement handlers

Expecting something to review on Tuesday. 


ERM-362 - Getting issue details... STATUS

steve.osguthorpe

Tenant API endpoints causes both agreements and licenses.

UXPROD-1755 - Getting issue details... STATUS

ERM-359 - Getting issue details... STATUS


Claudia Malzer

BE: h FE: h

  • Public / internal term values need to be handled 
  • (warning) consider term value notes refactor in future


  • Extend shape for new fields
  • Component affected: license terms list

UXPROD-1755 - Getting issue details... STATUS

ERM-355 - Getting issue details... STATUS Claudia Malzer

BE:  FE: 

  • Public / internal notes need to be handled in web-toolkit-ce
  • Public notes should not be hidden

UXPROD-1513 - Getting issue details... STATUS

ERM-290 - Getting issue details... STATUS

steve.osguthorpe

BE: expected Tuesday

  • ERM-333 Needs code review once delete functionality and ERM-349 completed
    • Everything in place.
    • TODO (BE): Error log display needs verifying (date stamp fix required)
  • ERM-334
    • TODO (BE): Requires delete functionality to be implemented; 
    • Front-end behaviour to be applied (return to the job list)
  • ERM-351 Front end integration tests
    • tests flaky against MCL
    • some more tests to be  written for view job details

UXPROD-1513 - Getting issue details... STATUS

ERM-217 - Getting issue details... STATUS  /  ERM-349 - Getting issue details... STATUS

steve.osguthorpe


UXPROD-1513 - Getting issue details... STATUS

ERM-217 - Getting issue details... STATUS  /  ERM-337 - Getting issue details... STATUS


Aditya matukumalli

UXPROD-1791 - Getting issue details... STATUS

ERM-332 - Getting issue details... STATUS

(tick)

Carried over for QA pending completion of  ERM-290 - Getting issue details... STATUS

UXPROD-1643 - Getting issue details... STATUS

ERM-338 - Getting issue details... STATUS

steve.osguthorpe

  • How to specify the errors for different types of source?

UXPROD-1643 - Getting issue details... STATUS

ERM-182 - Getting issue details... STATUS

steve.osguthorpe

BE 2h

UXPROD-1517 - Getting issue details... STATUS

ERM-265 - Getting issue details... STATUS

John Fereira

  • PR amends required:
    • indentation 
    • if statement
  • URL field data confirmed to be coming from pti
    • output QA'd 
    • happy to release once PR amends resolved

UXPROD-1517 - Getting issue details... STATUS

ERM-327 - Getting issue details... STATUS

Aditya matukumalli
  • Backend elements require code review
  • UI elements in place
  • UI conflicts re translation need resolving

UXPROD-1517 - Getting issue details... STATUS

ERM-215 - Getting issue details... STATUS

John Fereira

  • Duplicates issue resolved
  • TSV capability (ERM-325) included tinymce.emotions_dlg.help_16 
  • TODO: split coverage information needs calculating correctly
    • should this be two lines in the flat KBART file (question) Yes

UXPROD-1517 - Getting issue details... STATUS

ERM-328 - Getting issue details... STATUS

Aditya matukumalli

  • Should come at the same time as ERM-215
  • Frontend needs to be verified

UXPROD-1755 - Getting issue details... STATUS

ERM-356 - Getting issue details... STATUS

Owen Stephens

Would it be better to put public facing URL into OKAPI and serve that instead of increasing memory requirements through an additional Edge module?

Further clarification required.

JSON format to be defined (ERM-360)