ERM Sprint 84

ERM Sprint 84

Sprint Goal / Focus

  •  

Sprint Schedule

  • Sprint: 84

  • Release: Fameflower

  • Quarter: 2020 Q1

  • Start Friday 21 Feb, 2pm UK

  • Finish Friday 6 Mar, 12pm UK

 

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 

  • Back End Code Review:  

  • QA: 

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 

 

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-2081

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

FE: minor fill-in task

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

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

@Peter Böhm

Expected to take to mid-next week

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

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

@Peter Böhm

All backend work

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

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

@Ethan Freestone

Currently bundles in with callout tasks

Preference is to import properties (similar to Acquisitions approach). If so, this opens the door to making this a higher-order Stripes function. 

TODO: Ethan to refactor callout logic out of ERM-685 PR.

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

https://folio-org.atlassian.net/browse/ERM-668 / https://folio-org.atlassian.net/browse/ERM-684

@md331 (Deactivated)

Very positive feedback from users so far. One use case mentioned which may need a different approach.

Term filter requested to be pre-loaded on opening up, rather than blank query. 

TODO:

  • string subsets (should be added to the backend already)

  • set / not set (ERM-705)

  • look and feel

  • tests

 

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

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

@Aditya matukumalli  /   @steve.osguthorpe

Preference is for using UI labels is to do after Stripes internalisation library has been completed. 

If not hard-coding, then translation keys may need to be revised (normalisation and standardisation) to deliver this. Not necessarily clear correlation between label and field.

TODO:

  • select licenses functionality

  • report modal

  • progress indicator (if export is slow)

  • export report (backend)

No 'select all' functionality.

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

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

@Ethan Freestone

See notes on https://folio-org.atlassian.net/browse/ERM-685 above. 

TODO: Ethan to refactor callout logic out of ERM-685 PR and build out the generic functionality in either stripes-core or stripes-components. Need to liaise with Acquisitions. 

Next Stripes call is Thu 10am EST. Aim to have POC by then.

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

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

@Ethan Freestone

 

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

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

 

@Ethan Freestone

 

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

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

@Ethan Freestone

 

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

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

@Ethan Freestone

 

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

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

@Ethan Freestone

 

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

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

 

To confirm functionality is available (or effort needed if not) with @steve.osguthorpe.  Will be required to complete some of the query elements for ERM-684

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

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

 

TODO: 

  • Refactor backend types

  • Ensure correct default behaviours

  • Migrate existing data

 

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

 

Front-end stuff done. 

Split into front and back, and kick backend to Ready to Progress

Backend task created as https://folio-org.atlassian.net/browse/ERM-740

 

https://folio-org.atlassian.net/browse/ERM-655 / https://folio-org.atlassian.net/browse/ERM-427

@steve.osguthorpe

 

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

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

 

Not ready for QA

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

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

 

Elaborate subtasks