ERM Sprint 123

ERM Sprint 123

Sprint Goal / Focus

  • Stripes 7 Upgrade

  • Bug fixes

  • RTL migration

Sprint Schedule

  • Sprint: 123

    • Start Monday 13 Sep

    • Finish Fri 24 Sep

    • Sprint Board

    • Jira Sprint: 1003

  • Release: 2021.3 Kiwi  

    • Sprint 123 (Mon Sep 13): Stripes v7 Upgrade Deadline

    • Sprint 124: Module Release Deadline

    • Sprint 127: Bugfix Deadline

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • 20-24 Sep: Peter on Leave

Lead Roles:

  • Front End Code Review: @Aditya matukumalli

  • Back End Code Review: @Ethan Freestone

  • QA: @Owen Stephens

QA Environment: folio-snapshot

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/UXPROD-3264

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

@Aditya matukumalli

All branches pushed except ui-stripes-registry and dashboard which are pending platform-complete.

There is an issue with having ui AND stripes in name that is causing conflict, though this was previously advised by John M. 

Adi to discuss on #devops options to either change repository name or amend code that does name checking. 

Dashboard is unreleased, but dependent on the decision for ui-stripes-registry. 

Proceed with merge depending on whether deprecation happens before Stripes merge

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

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

@Ethan Freestone

 

 

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

@Claudia Malzer

Estimate 1d

May need update to filter.js 

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

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

@Claudia Malzer

When an agreement references more than 10 PO lines, we construct a query that caps results to 10. We should now show all requested lines. 

Add new CONST to manifest similar to RecordsPerRequest for orderlines from 100 to 1000. 

Starting points are AgreementLineRoute and AgreementLineViewRoute, and make changes to ask for higher maximum return limit parameter. 

Apply to view and edit. 

https://folio-org.atlassian.net/browse/FAT-81

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

@Claudia Malzer

 

https://folio-org.atlassian.net/browse/FAT-81

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

@Claudia Malzer

 

https://folio-org.atlassian.net/browse/FAT-81

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

@Aditya matukumalli

 

https://folio-org.atlassian.net/browse/FAT-81

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

@Claudia Malzer

 

 

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

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

May need changes to toolkit also, so best done by a K-Int resident.

Could have conflicts with core vagrant update. 

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

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

 

 

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

@Ethan Freestone

@Aditya matukumalli

Will require stable vagrant - latest version should be sufficient to develop with.

Frontend can be done in anticipation. 

Presentation should be similar to existing pattern, so no new wireframes needed. 

TODO: 

  • Add new example to custom properties (0.5h backend)

  • Changes to ui-agreements and erm-components (1h + overnight build on snapshot/testing)

 

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

 

 

 

 

 

@Aditya matukumalli

TODO: raise draft PR for implementation review

Related (still blocked):

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

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

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

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

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

 

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

@Ethan Freestone

 

 

 

 

Brought Forward

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

@Peter Böhm

@Ethan Freestone

TODO:

  • Modify to remove duplicate entries

  • Enhance integration test to match issue 

 

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

@Aditya matukumalli

Branch for stripes-components reviewed by John C.

Edge cases to be handled STCOM-865.

 

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

@Peter Böhm

Review on Wednesday

 

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

@Monireh Rasouli

Minor changes needed to 1345-1349

 

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

@Monireh Rasouli

To pick up Tuesday

For QA / Release

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Brought In

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

 

 

 

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

 

 

Removed

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

@Gill Osguthorpe

New tests prepared and submitted for Boulder user testing.  

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

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

 

Bug fixes ahead of Kiwi release to take priority

 


Sprint Summary

 

ERM

 

key summary type assignee status components
Loading...
Refresh

 

Dashboard

key summary type assignee status components
Loading...
Refresh

Other

key summary type assignee status components
Loading...
Refresh