ERM Sprint 73

ERM Sprint 73

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 73

  • Release: Elderflower

  • Quarter: 2019 Q4

  • Start Monday 23 Sep, 2pm UK

  • Finish Friday 4 Oct, 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions: NA

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 

 

Brought Forward (from previous sprint)

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

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

@Claudia Malzer

TODO:

  • Add/rename endpoints to "current" / "future"/"dropped" / "all" (backend - @steve.osguthorpe )

  • Front-end design/integration + tests

@Owen Stephens to add custom package test data to Jira issue to use for integration tests

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

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

@Claudia Malzer

TODO: 

  • uses "current" endpoint being implemented as part  of ERM-396

  • original path shows 'all' resources - just need to show 'current'

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

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

@Peter Böhm

Count not incrementing for ERM-404 & ERM-407.

Not holding anything else up

Not as high priority as UXPROD-1467 tasks

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

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

@Peter Böhm

Counts not incrementing

Not as high priority as UXPROD-1467 tasks

 

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

@Ethan Freestone

Related to but not blocked by forthcoming release of https://folio-org.atlassian.net/browse/STCOM-567.

TODO: 

  • Some minor changes to PR

  • Tests to follow (@md331 (Deactivated))

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

https://folio-org.atlassian.net/browse/ERM-356 / https://folio-org.atlassian.net/browse/ERM-361

@steve.osguthorpe

Nearly done. TODO: 

  • Finish templating for the terms

Should be less than 1hr work

 

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

Requires UI for https://folio-org.atlassian.net/browse/ERM-394 in order to QA.

Fixed: PR pending. 

 

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

@Owen Stephens

Ready for QA, once re-deploy complete.

 

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

UXPROD-1932: Manage resources joining/leaving an AgreementClosed

ERM-456: Manage Agreement line Active datesClosed

@Aditya matukumalli

Front-end only.

UXPROD-1932: Manage resources joining/leaving an AgreementClosed

ERM-457: Use Agreement Line active from/active to dates when calculating current/expected/previous content of agreementClosed

@steve.osguthorpe

Back-end only. Will deliver as part of backend updates for ERM-394 and ERM-396. 

UXPROD-1467: "Renew" an agreementClosed

ERM-466: Manage Agreement periodsClosed

@md331 (Deactivated)

BE: 1d FE: 3d

 

UXPROD-1467: "Renew" an agreementClosed

ERM-467: Display Agreement periodsClosed

@md331 (Deactivated)

Requires ERM-466: Manage Agreement periodsClosed back-end model, which will include calculated/derived dates. 

  • All periods provided as list

  • Current period to be provided on own

Incorporate as part of ERM-466

UXPROD-1467: "Renew" an agreementClosed

ERM-468: Use current Agreement period in place of Agreement start/end datesClosed

@md331 (Deactivated)

Requires ERM-466: Manage Agreement periodsClosed back-end model

Incorporate as part of ERM-466

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

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

@Aditya matukumalli

BE: 1h FE: 3d

Wireframes not necessary in this case. 

Out of scope: configuration of closure reasons

TODO: 

  • Store closure reasons in tenant initialisation file

  • Migrate Cancelled status to Closed status

  • New 'Reason for closure' property

  • UI + tests

 

Carried Forward (to future sprint)

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions