ERM Sprint 74

ERM Sprint 74

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 74

  • Release: Elderflower

  • Quarter: 2019 Q4

  • Start Monday 7 October, 2pm UK

  • Finish Friday 18 October 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • @Claudia Malzer on vacation (Japan) from Wed 9 Oct

Lead Roles:

  • Front End Code Review: @md331 (Deactivated)

  • Back End Code Review:  @steve.osguthorpe

  • QA: @Owen Stephens

QA Environment: folio-testing

Navigation

  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  

 - not in sprint

 or @ - in sprint 

 

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

https://folio-org.atlassian.net/browse/ERM-498

@steve.osguthorpe@md331 (Deactivated)

BE: 1h FE: 1d

  • Split log retrieval end points (info, error, all)

  • Add count for each end point per job

  • Update accordians to use new endpoints

https://folio-org.atlassian.net/browse/UXPROD-1467

https://folio-org.atlassian.net/browse/UXPROD-1470

https://folio-org.atlassian.net/browse/UXPROD-584

https://folio-org.atlassian.net/browse/ERM-460

@md331 (Deactivated)

BE 1d FE 5d

Potentially a single endpoint for both incoming and outgoing relationships (two separate properties)

Or, having action endpoints per agreement (potentially more extensible)

More investigation required. 

https://folio-org.atlassian.net/browse/UXPROD-1467

https://folio-org.atlassian.net/browse/ERM-459

@Aditya matukumalli

BE   FE 

Different objects are duplicated in different ways - sometimes you need a copy of the ID, rather than the same ID. 

Should be able to do UI separate to back-end, up to the point of saving.  Back-end processing to follow. 

Cleanest way is to clone and save an agreement, and then treat it as an edit on the new agreement.  

TBD: ported values of Start & End Dates of Agreement Period

FE needs to know format of what the BE will send/consume (object or string array likely - FE to decide).

https://folio-org.atlassian.net/browse/UXPROD-1467

https://folio-org.atlassian.net/browse/ERM-497

FE 1h

Current period should be NULL, and has a key on the agreement. Needs to use that instead.

Common approach to handling these is required.

https://folio-org.atlassian.net/browse/ERM-493

@Owen Stephens  @Gill Osguthorpe

FE 2h (excluding tests)*

Change to show a button tooltip that shows a user doesn't have permission.

* Tests for permissions based stuff like this is not manageable.

Common approach to handling these is required.

https://folio-org.atlassian.net/browse/ERM-495

@Owen Stephens  @Gill Osguthorpe

 

Common approach to handling these is required.

https://folio-org.atlassian.net/browse/ERM-496

@Owen Stephens  @Gill Osguthorpe

 

https://folio-org.atlassian.net/browse/UXPROD-1669

https://folio-org.atlassian.net/browse/ERM-283

Still blocked by STCOM-576

Brought Forward

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions