Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 AvailabilitySchedule

Notes / Exceptions:

Lead Roles:

QA Environment: folio-testing

Navigation

Table of Contents

Expand
titleSprint 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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1669

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-306

Carried over for QA

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-274

BE: 6h FE: 0h

TODO: implement handlers

Expecting something to review on Tuesday. 


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-362

Tenant API endpoints causes both agreements and licenses.

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1755

Jira
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-357359


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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1755

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-355
Claudia Malzer

BE:  FE: 

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1513

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-290

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1513

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-349


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1513

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-217
 / 
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-337


Aditya matukumalli

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1791

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-332

(tick)

Carried over for QA pending completion of 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-290

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1643

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-338

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1643

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-182

BE 2h

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-265

  • 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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-327

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-215

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-328

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1755

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-356

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)