Skip to end of banner
Go to start of banner

ERM Sprint 84

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

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 Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

  • Front End Code Review: 
  • Back End Code Review:  
  • QA: 

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-2081 - Getting issue details... STATUS

ERM-708 - Getting issue details... STATUS

(tick)FE: minor fill-in task

UXPROD-2081 - Getting issue details... STATUS

ERM-689 - Getting issue details... STATUS

Peter Böhm

Expected to take to mid-next week

UXPROD-2081 - Getting issue details... STATUS

ERM-681 - Getting issue details... STATUS

Peter Böhm

All backend work

UXPROD-1514 - Getting issue details... STATUS

ERM-685 - Getting issue details... STATUS

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.

UXPROD-1478 - Getting issue details... STATUS

ERM-668 - Getting issue details... STATUS  /  ERM-684 - Getting issue details... STATUS

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


UXPROD-1478 - Getting issue details... STATUS

ERM-713 - Getting issue details... STATUS

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.

UXPROD-2125 - Getting issue details... STATUS

ERM-723 - Getting issue details... STATUS

Ethan Freestone

See notes on ERM-685 - Getting issue details... STATUS  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.

UXPROD-2125 - Getting issue details... STATUS

ERM-724 - Getting issue details... STATUS

Ethan Freestone


UXPROD-2125 - Getting issue details... STATUS

ERM-725 - Getting issue details... STATUS


Ethan Freestone


UXPROD-1669 - Getting issue details... STATUS

ERM-726 - Getting issue details... STATUS

Ethan Freestone


UXPROD-1669 - Getting issue details... STATUS

ERM-727 - Getting issue details... STATUS

Ethan Freestone


UXPROD-1669 - Getting issue details... STATUS

ERM-730 - Getting issue details... STATUS

Ethan Freestone

UXPROD-1478 - Getting issue details... STATUS

ERM-705 - Getting issue details... STATUS


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

UXPROD-2258 - Getting issue details... STATUS

ERM-735 - Getting issue details... STATUS


TODO: 

  • Refactor backend types
  • Ensure correct default behaviours
  • Migrate existing data

ERM-715 - Getting issue details... STATUS


Front-end stuff done. 

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

ERM-655 - Getting issue details... STATUS  /  ERM-427 - Getting issue details... STATUS

steve.osguthorpe


UXPROD-2251 - Getting issue details... STATUS

ERM-700 - Getting issue details... STATUS


Not ready for QA

UXPROD-2251 - Getting issue details... STATUS

ERM-702 - Getting issue details... STATUS


  • Elaborate subtasks
  • No labels