Versions Compared

Key

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

Sprint Goal / Focus

  • Improvements to Entitlement Log
  • Dashboard UI

Sprint Schedule

  • Sprint: 125
    • Start Mon 11 Oct
    • Finish Fri 22 Oct
    • Sprint Board
    • Jira Sprint: 1040
  • 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 AvailabilitySchedule | Calendar

Notes / Exceptions:

  • 11-12 Oct: Ethan on leave
  • 11-15 Oct: Ian on leave
  • 13 Oct: Adi 0.5d
  • 15 Oct: Peter not on ERM
  • 18 Oct: Adi 0.5d
  • 21-22 Oct: Adi on leave
  • 22 Oct: Peter not on ERM

Lead Roles:

QA Environment: folio-snapshot


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 


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

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3335

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1850

  • Approach
    • Improve usability of kb
  • Components and Changes
    • Frontend: none
    • Backend: mod-agreements ResourceController
  • Tests / Data: none
  • Dependencies: none
  • Known Unknowns: none
  • QA
    • environment: locally - because of daily title-harvest
    • data: set up a harvest for title-only data
  • Development Estimate: 2d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2817

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1459

  • Approach: 
    • Complete review for user story gap analysis
    • New stories to be added for Lotus as needed

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2817

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1882

  • Approach
  • Components and Changes
    • Frontend: none
    • Backend:
      • mod-agreements: update _entitlementLogEntry.gson to work more like _entitlement.gson
  • Tests / Data: / Dependencies: none
  • Known Unknowns: none
  • QA
    • environment: snapshot 
    • data / scripts: none
  • Development Estimate: <1d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2817

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1884
/
Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1900

Ethan Freestone
  • Approach
    • suppress entry needs to be persisted on entitlement log
    Components
    • update between timed runs would not be caught
  • Components and Changes
    • Frontend
    • Backend: Update logic to handle suppressed fields in mod-agreements
  • Tests / Data: none
  • Dependencies: 
    • suppress field handling on ERM-1883
      • no means currently to handle log updates
    • need some kind of infrastructure to support recording when a field on a resource is changed
  • Known Unknowns: no
  • QA
    • environment: local | testing | snapshot | other
    • data
    • scripts
  • Development Estimate: <1d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2817

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1883


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1888

  • Approach
    • ERM-1889 Create re-usable status component
    • The newly displayed fields are not editable - hence new component needed, similar to agreements meta
    • existing meta section component in FOLIO is not suitable
  • Components and Changes
    • Frontend:
      • stripes-erm-components:
        • set up stripes-erm-components for RTL tests
        • add new component for metadata status
        • add styling (reuse from meta section)
        • support dynamic fields as children prop
        • add translation support for dynamic fields
        • render as an accordian (re-use from stripes-components)
        • pass first line as accordian label prop
        • verify inherited accessibility treatment
      • ui-local-kb-admin: 
        • set up ui-local-kb-admin for RTL tests
        • add translation keys for labels
        • always render the component
        • add display logic to externalDataSourcesView.js
    • Backend: none
  • Tests:
    • ui-local-kb-admin
    • stripes-erm-components
  • Data: no
  • Dependencies: none
  • Known Unknowns:
    • name of component
  • QA
    • environment: snapshot
  • Development Estimate
    • status component: 2d
    • lkb: 2d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3336

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1687

  • Approach
    • Add validation to FieldArray  - already in place
    • Check field meta, such as whether it is touched (as opposed to dirty)
    • Compare with how similar is handled with overlapping dates
    • Recent changes
      • ERM-1826
      • ERM-1688 - autofocus behaviour changed to now remains on Add Column, which means validation doesn't fire (only fires on touched fields)
  • Components and Changes
    • Frontend: ui-dashboard
    • Backend: none
  • Tests / Data / Dependencies: 
    • Adi to Fix Save and Close on issue
    • Ethan to verify consistency of validation pattern 
  • Known Unknowns
    • FieldArray validation already exists, 
    • Not clear why this would be different to other field arrays
  • QA
    • environment: snapshot 
    • data / scripts: no
  • Development Estimate: unknown

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3336

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1855

  • Components and Changes
    • Frontend: ui-dashboard
    • Backend: none
  • Tests/ Data : none
  • Dependencies: none
  • Known Unknowns: none
  • QA: snapshot
  • Development Estimate: <0.5d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3336

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1792

  • Approach
  • Components and Changes
    • Frontend: ui-dashboard
    • Backend: none
  • Tests/ Data : none
  • Dependencies: none
  • Known Unknowns: none
  • QA: snapshot
  • Development Estimate: <0.5d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1467
/
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1468
/
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1472

  • Approach: RTL Migration
  • Components and Changes
    • Frontend: ui-agreements
    • Backend: none
  • Dependencies: None
  • Known Unknowns: coverage gaps
  • QA: NA
  • Development Estimate









Rolled Over From Previous Sprint

For Development

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1259

For Code Review

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1258

For Code Review

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1287

For Code Review

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1852

For Code Review

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1661

More complex, and to be picked up after simpler tests and feature work: 

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1666
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1676
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1669

This sprint:

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1670
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1678



Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1700

Issues with adding users to workspace

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3338

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1813

Previously TODO:

Planning

  • QA
    • environment: local | testing | snapshot | other
    • data
    • scripts
  • Development Estimate: aim for code review Wed/Thu

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3336

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1791


For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3339

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1798

Additional functionality added for creating print instance. Needs to be re-tested. 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3336

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1688

Owen Stephens

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1704


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1754

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1891

Required for Kiwi 

Agreement lacks any items, so no list is presented. Since changes for ERM-1754.

  • Approach
    • concern that this might break ERM-1754
    • should we derive list from entitlements, as per view screen?
      • chosen approach avoids submitHandler
    • Will need expedited release ahead of Bugfest
  • Components and Changes
    • Frontend: none
    • Backend: mod-agreeements
  • Tests / Data: no
  • Dependencies: ERM-1754
  • Known Unknowns: no
  • QA
    • environment: snapshot & bugfest
    • data / scripts
  • Development Estimate

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFAT-81

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1285

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1290

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1291

Development Estimate: <2d

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1892

Ethan Freestone

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySTRIPES-769

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1893

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1894

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1895

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1896

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1897

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyERM-1897-90f1-ee9b165564fc
keyERM-1898

Stripes fixes: update react-intl-safe-html to v3.1

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3372

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1890


Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2817

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1900

Split from ERM-1884, and dependent on update mechanism developed as part of ERM-1883

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-18981903

Stripes fixes: update react-intl-safe-html to v3.1

Removed

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3156

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1757

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1758

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1759

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1760

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1761

  • Approach
  • Components and Changes
    • Frontend:
      • ui-agreements
      • ui-licenses
      • ui-erm-comparisons
      • ui-local-kb-admin
      • ui-dashboard
    • Backend: none
  • Tests
  • Data
  • Dependencies
    • PR #1565  for STCOM-865 is closed without merging, and no longer is required for or blocks these issues
    • PR #1617 for STCOM raised and pending review
      • merge block for Kiwi release removed 
  • Known Unknowns
  • QA
    • environment: local | testing | snapshot | other
    • data
    • scripts
  • Development Estimate

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3337

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-1842

(error)
  • No longer an issue







Sprint Summary

ERM


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


Dashboard

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

Other

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