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:

Lead Roles:

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 

 

Sprint Focus

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-498 - Getting issue details... STATUS

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

UXPROD-1467 - Getting issue details... STATUS

UXPROD-1470 - Getting issue details... STATUS

UXPROD-584 - Getting issue details... STATUS

ERM-460 - Getting issue details... STATUS

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. 

UXPROD-1467 - Getting issue details... STATUS

ERM-459 - Getting issue details... STATUS

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).

UXPROD-1467 - Getting issue details... STATUS

ERM-497 - Getting issue details... STATUS

(tick)

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.

ERM-493 - Getting issue details... STATUS

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.

ERM-495 - Getting issue details... STATUS


Common approach to handling these is required.

ERM-496 - Getting issue details... STATUS


UXPROD-1669 - Getting issue details... STATUS

ERM-283 - Getting issue details... STATUS

(error)Still blocked by STCOM-576

Brought Forward

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-1469 - Getting issue details... STATUS

ERM-465 - Getting issue details... STATUS

Migration of status aspect to be QA'd by steve.osguthorpe.

UXPROD-1469 - Getting issue details... STATUS

ERM-483 - Getting issue details... STATUS

Subsumed as scenario of  ERM-465 - Getting issue details... STATUS .  To be QA'd by steve.osguthorpe

UXPROD-585 - Getting issue details... STATUS

ERM-392 - Getting issue details... STATUS


UXPROD-585 - Getting issue details... STATUS

ERM-393 - Getting issue details... STATUS


UXPROD-585 - Getting issue details... STATUS

ERM-394 - Getting issue details... STATUS

Awaiting integration tests. Expected to complete within next day.

UXPROD-585 - Getting issue details... STATUS

ERM-396 - Getting issue details... STATUS

Awaiting integration tests. Expected to complete within next day.