Versions Compared

Old Version 1

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version Current

changes.mady.by.user Jag Goraya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Goal / Focus 

  • 22 Mar: Module Release Deadline

Sprint Schedule

  • Sprint: 188
  • Release: 2024.1 Quesnalia 
    • Sprint 11 of 11 since Release Development Cycle Starts (Sprint 176) to Feature Freeze (Sprint 186: 15 Mar 2024)
    • Sprint 187: Module Release Deadline (22 Mar 2024) [FOLREL-565]
    • Sprint 189: Bugfix Release Deadline (19 Apr 2024) [FOLREL-581]

Development Meetings

  • Wed 6 Mar - dev update
  • Mon 11 Mar - backlog review
  • Wed 13 Mar - dev update

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present


Info
titlePlanning 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

Table of Contents

Expand
titleSprint 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 

(warning) - not ready

(question) - pending triage / planning

Sprint Focus

Info
iconfalse
titlePlanning Notes Template

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate



Serials

  • Ethan Freestone
    • Determine pattern for tests on react query hooks or useMutation,
    • async function in ky library chains a .then promise, which is not easily tested
  • Monireh Rasouli 
    • memory routing on index.js in /src and /settings
  • Jack Golding
    • Resolve code smells (tick)
    • Revise longstanding TODOs as Jira issuesissues (tick)
    • Prioritise: 
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUISER-88
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUISER-99
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUISER-13
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUISER-100
        • needs test
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUISER-113
        • on hold


Open Access

  • Separate module and interface versions
  • Upgrade to Grails 6
  • Complete QA on UIOA-215
  • Release


IssueSprint Backlog?NotesCarried Over
Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3161
(error) Moved to Ramsons

 

  • Release additional logging as ERM-3191
  • Trace zombie job behaviour - there may be an overlap of functionality
  • Add special checks that is not locked

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3191
Jack Golding
  • Release additional logging for ERM-3161

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-3182
Claudia Malzer





















































































Grails Track

 

  • Success with compiling and running with Grails 6
  • However, JobRunner is not behaving as expected: 
    • unchanged between 5 and 6 
    • but jobs are not being picked up
    • probably an unnecessary transaction that has been added and is now scoped

 

  • JobRunner triage indicates some client level tasks need tenant scope
    • These can fail silently
  • TODO:
    • diagnose cause of JobRunner fail
    • review areas where this may similarly occur (is this a job issue or pattern issue)
  • UNKNOWN
    • whether this affects beyond mod-0agreements: unlikely as it is related to federation interface with database

 

  • Running out of resources when running harvest on local branch
  • Not reproduced on master, so using that with postgres to get some perfomance data to compare

 

  • mod-agreements
    • compiles, builds, run
    • harvest begins, but goes from 20% CPU usage to 30-90 before climbing to 1005%
  • could be a local laptop issue
  • dev note: set up new application.yaml for an isolated pg/kafka environment to test performance 

 

  • QA pending


  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-3111
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-3089
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keySI-34
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keySI-38
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-3090


Tests

(minus) Cypress test development stalled pending implementation of

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySTCOR-484

Issue ID

Sprint Backlog?

Notes / Estimates / Actions





Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Quesnalia)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA

Release Tasks (Poppy Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA







Sprint Summary

ERM


Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels != release and labels in (licenses, agreements, erm) and Sprint = 111 and issuetype in standardIssueTypes()
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Dashboard

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels = dashboard and Sprint = 111
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,assignee,status,components,labels
columnskey,summary,type,assignee,status,components,labels
maximumIssues20
jqlQuery(labels = release or labels not in (licenses, agreements, erm, dashboard)) and Sprint = 111
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

No Label

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels is empty and Sprint = 111
serverId01505d01-b853-3c2e-90f1-ee9b165564fc