Skip to end of banner
Go to start of banner

ERM Sprint 127

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 4 Next »

Sprint Goal / Focus

  • Bugfest
    • mod-agreements
    • ui-agreements
  • RTL Migration

Sprint Schedule

  • Sprint: 127
    • Start Mon 8 Nov
    • Finish Fri 19 Nov
    • Sprint Board
    • Jira Sprint: 1082
  • Release: 2022.1 Lotus  
    • Sprint 133: Module Release Deadline
      • Backend 16 Feb 2022
      • Frontend 18 Feb 2022
    • Sprint 136: Bugfix Deadline (25 March 2022)

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • 8 Nov: Monireh on leave
  • 9-10, 16 Nov: Adi 0.5d

Lead Roles:

QA Environment: folio-snapshot

Planning Questions

  • Does the issue meet the criteria for Definition of Ready?
  • What front and back end components are affected?
  • What changes need to be made? (additions, removals or modifications)
  • What development tests need to be written?  
  • What data does the developer need to verify their work?
  • What are the known unknowns? 
  • What is needed to QA? (environment, data, scripts)

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 


Planning Notes Template

  • Approach
  • Components and Changes
    • Frontend
    • Backend
  • Tests / Data
  • Dependencies
  • Known Unknowns
  • QA
    • environment: local | testing | snapshot | other
    • data / scripts
  • Development Estimate

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions


ERM-1917 - Getting issue details... STATUS

Ethan Freestone 
  • Approach
    • fixes initial problem
    • should not appear for title first matching
    • TODO
      • commit changes
      • run against integration tests
      • release
      • add note to migration issue (ERM-1820) to remove  unmapped mitigation
  • Components and Changes
    • Frontend: none
    • Backend: mod-agreements
  • Tests / Data: none
  • Dependencies: none
  • Known Unknowns
    • no new instances expected, but any existing anomalies will not be caught
  • QA
    • environment: local + snapshot
    • data / scripts: none
  • Development Estimate: push to master today

ERM-1687 - Getting issue details... STATUS

Aditya matukumalli 

Needs investigation.  

  • Approach
    • issue where the component is not being touched
    • TODO check with John Coburn for similar patterns
  • Components and Changes
    • Frontend: ui-agreements
    • Backend
  • Tests / Data
  • Dependencies
  • Known Unknowns
  • QA
    • environment: local | testing | snapshot | other
    • data / scripts
  • Development Estimate

ERM-1757 - Getting issue details... STATUS

ERM-1758 - Getting issue details... STATUS

ERM-1759 - Getting issue details... STATUS

ERM-1760 - Getting issue details... STATUS

ERM-1761 - Getting issue details... STATUS

Claudia Malzer 

https://github.com/folio-org/stripes-components/pull/1617 has been approved, but not merged

  • Approach
    • see comment on https://github.com/folio-org/stripes-components/pull/1617#issue-999577279
    • see readme on readme.md
    • can import defaultKeyboardShortcuts (all) or the appSpecificShortcuts to specify only those required
    • can renamedShortcuts to alter label in specific
      • needs to be translateable string
    • pass renamedShortcuts to shortcuts modal
    • do not need to import copy, cut, paste, find, close, open as they are folio wide and automatically included
  • Components and Changes
    • Frontend: components as per issues
    • Backend: none
  • Tests / Data: not needed
  • Dependencies: none
  • Known Unknowns: 
    • can selectively order multiple shortcuts by comma separation
    • shortcuts are ordered as per Guideline 2
  • QA: Gill 
    • environment: snapshot 
    • data / scripts: none
  • Development 3d. Code Review Wed

ERM-1841 - Getting issue details... STATUS

Gill Osguthorpe 

Subject to 

UXPROD-3337 - Getting issue details... STATUS


Owen Stephens 

ERM-1906 - Getting issue details... STATUS

ERM-1907 - Getting issue details... STATUS

ERM-1908 - Getting issue details... STATUS

ERM-1909 - Getting issue details... STATUS

ERM-1910 - Getting issue details... STATUS

ERM-1911 - Getting issue details... STATUS

  • Approach
    • controlled vocabulary has new as part of the component
    • this would be a pattern change, so raises concerns about ux consistency
      • would also get technically messy (switches off some given elements and adds them elsewhere)
    • potentially create a pattern to pass the component through
      • eg, change pane, check pane rendering
    • story needs revisiting: goal is to keep New button visible (not necessarily in top bar)
  • Known Unknowns
  • TODO: 
    • Owen to revisit story descriptions 
    • Discuss in dev call on Wednesday








Rolled Over From Previous Sprint

For Development

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1915 - Getting issue details... STATUS

Aditya matukumalli 

  • Approach
    • OS to add test cases
    • mount and update lifecycles of view pane
    • Change to stripes-connector fetches: manual rather than single references because of chunking
    • lengths > 3k characters are failing, rather than 4096 
      • hence limited to 5 concurrent with 60 ids 
  • Components and Changes
    • Frontend: ui-agreements
  • Tests / Data: none
  • Dependencies: none
    • release issue to be created
  • Known Unknowns
    • scaling with larger dataset: OS to test
  • QA
    • environment: bugfest data, local ui
    • data / scripts: new 1k order line example spread across agreement lines to be set up (eg, 150 POL  x 6 AL)
  • Development Estimate:
    • QA and release today

FAT-81 - Getting issue details... STATUS

ERM-1913 - Getting issue details... STATUS

Aditya matukumalli 


FAT-81 - Getting issue details... STATUS

ERM-1661 - Getting issue details... STATUS / ERM-1666 - Getting issue details... STATUS

Aditya matukumalli 


FAT-81 - Getting issue details... STATUS

ERM-1472 - Getting issue details... STATUS

Monireh Rasouli 

PR #914 still outstanding

FAT-81 - Getting issue details... STATUS

ERM-1487 - Getting issue details... STATUS



FAT-81 - Getting issue details... STATUS

ERM-1489 - Getting issue details... STATUS



FAT-81 - Getting issue details... STATUS

ERM-1495 - Getting issue details... STATUS



FAT-81 - Getting issue details... STATUS

ERM-1494 - Getting issue details... STATUS




ERM-1902 - Getting issue details... STATUS

Ethan Freestone 

Incorprating: 

ERM-1900 - Getting issue details... STATUS

ERM-1883 - Getting issue details... STATUS


ERM-1850 - Getting issue details... STATUS

Peter Böhm 



ERM-1904 - Getting issue details... STATUS

(question)

For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


 ERM-1882 - Getting issue details... STATUS

Owen Stephens 



ERM-1884 - Getting issue details... STATUS

Owen Stephens 


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1791 - Getting issue details... STATUS

Owen Stephens 



ERM-1813 - Getting issue details... STATUS

Owen Stephens 



ERM-1888 - Getting issue details... STATUS

Owen Stephens 



ERM-1688 - Getting issue details... STATUS

Owen Stephens 


Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

ERM-1916 - Getting issue details... STATUS

ERM-1914 - Getting issue details... STATUS

Owen Stephens Closed - already released

Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Removed

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions











Sprint Summary

ERM


key summary type assignee status components
Refresh


Dashboard

key summary type assignee status components
Refresh

Other

key summary type assignee status components
Refresh

  • No labels