Versions Compared

Key

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

Sprint Goal / Focus

  • 16 Sep: Orchid Release Plans

Sprint Schedule

  • Sprint: 147
  • Release: 2022.3 Nolana  
    • Sprint 8 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
    • Sprint 151: Module Release Deadline [FOLREL-549]
      • Backend 26 Oct 2022
      • Frontend 28 Oct2022
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

Development Meetings

  • 7 Sep 2022
  • 14 Sep 2022

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Monireh: A/L Sprint Week 1 (5-9 Sep)
  • Peter: A/L Sprint Week 2 (12-16 Sep)

Lead Roles:

QA Environment: folio-snapshot

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 


Info
iconfalse
titlePlanning Notes Template
  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

No dev action for now. Potentially can drop secondary lookup for Gokb and speed up job performance.

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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

No dev action for now. May result in UI changes. 

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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

Fallout from ERM-2314

Currently :

  • Every single user has a default dashboard on first Dashboard access

Issue;

  • Cannot rely on existing mydashboard  default
  • Not all users will have a mydashboard 

TBD:

  • Prompt to create a dashboard or assign an existing dashboard as default when accessing Dashboard app
  • Owen to review desired behaviour

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Nolana)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Brought In

Issue ID

Sprint Backlog?

Notes / Estimates / Action




Removed

Issue ID

Deferred to

Notes / Estimates / Actions








Info
titlePlanning Notes Template
  • Current State
  • TODO
  • Development Estimate

Rolled Over From Previous Sprint

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions

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

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

  • Current State
    • tested and working on gokb
    • had to set up frontend to test cursor
      • being hikari issue identified 
      • known hikari issue experienced which is not to be addressed
  • TODO
    • complete testing on on kbart
      • not sure how to test source updates, such as lifecycle
      • potentially not set initially from kbart
    • code cleanup and then PR
  • Development Estimate
    • Wed 10
  • TODO
    • fix removeFrom error
      • replace `it.contentTypes` with `it`
    • fix each-iterator error
      • ensure happening within transaction
      • attempt to save without flushing, to avoid trying something new
    • re-test
  • Development Estimate: 

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

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

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

    • Sorting: not expected for volumes of users expected in list (~10)
    • Is name handed from Users as a single name, or first/last name?
      • To be consistent across FOLIO, we should keep separate
    • Out of scope: giving user list access to non-manager users
    • Does Users pre-filter out inactive users?
  • QA: snapshot | local | testing | other

  • Development EstimateCurrent State
    • some backend changes
  • TODO
    • check validation pattern for multiple user use-case with Gill
    • tests
  • Development Estimate: 2.5d
NA

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

  • Current StateDevelopment Estimate: <1d
    • No progress started
    • Previously rewritten to a single component
      • that may be covered for tests
  • TODO
    • extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
    • tweak test for getResourceIdenitifier
    • update ui-agreements to apply logic
    • add tests to eResourceIdentifier to check multiple cases
    • Parking test centralisation until approach has been defined
    • sonarLint changes is resolved
    • stripes list / list-item interactors is not ready to use yet: 
  • TODO
    • tests need to be done for ui-agreements,, using html interactor as workaround for list
      • nothing shows up
      • 1 thing shows up
      • multiple things show up
  • Development Estimate: 


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

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

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2311
  • Approach

    • add to package schema
    • add fields to ingest 
    • update adaptor
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: packageViewSpec.groovy 

    • add to existing JSON object
    • add new test for fields/filters (on Set) 
    • add new test for update
  • Dependencies: ERM-2288

  • Known Unknowns: 

  • QA: snapshot

  • Development Estimate: Monday

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

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2307
(question)(error)
  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements (adaptor)

  • Tests / Data: none

  • Dependencies:

    • requires ERM-2306

    • enables ERM-2308
  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: == ERM-2311

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

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

(question)
  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor
  • Components and Changes

    • Frontend: yes

    • Backend: none

  • Tests / Data: none

  • Dependencies:

    • ERM-2306

    • Gill to review frontend mockups based on ERM-2306 shape
  • Known Unknowns: none 

    • properties are in json, but not in gokb (ERM-2307)
      • Owen to provide JSON file
  • QA: snapshot

  • Development Estimate: == ERM-2311

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

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

(question)
  • Approach

    • lookup the refdata
    • query refdata
    • filter on list
    • use selection add accordian to package filters (Availability Constraints)
    • show list similiar to Tags  / External Source Data
    • use multiselect rather than checkboxes doing lookup
    • publicationType is checkboxes - so, OR'd in filter, rather than AND
      • no default to be set 
      • no lookahead for now
    • filter on selection
  • Components and Changes
    • Frontend: ui-agreement

    • Backend: none

  • Tests / Data:

    • if we already have existing filter tests

  • Dependencies: ERM-2306

  • Known Unknowns

    • list size may encourage select rather than checkboxes
      • confirmed: expecting to be in the order of 10s, rather than 100s
      • therefore use single call (as opposed to tags)
  • QA: snapshot 

  • Development Estimate: 1d

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

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

(question)(error)
  • Approach

    • add new logic to packageIngestService lines 212-218
    • ensure save after block
    • use existing patterns for updating PTI
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements packageIngestService 

  • Tests / Data: package test data

  • Dependencies: no

  • Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: small


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

(error)

Approach:

  • Can mock pluggable to check if plugin shows up
  • Check if card is displayed

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


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

(error)

Pending Dependency: ERM-2316. 

Moved to Sprint 149 to coincide with ERM-2316

In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

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

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

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

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


Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySTSMACOM-678

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



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



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


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

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


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

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


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

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



For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

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

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

  • Approach

    • Owen to update issue
    • Delete dashboard: present warning
    • Scenario 5: show user access level
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

    • No tests to be written
  • Dependencies

    • Should amend the current behaviour to not create a new dashboard in the backend, so a user comes to a splash screen on first access
      • Ethan to stub an issue for Owen to review and prioritise after ERM-2314
      • Est: 0.5d to add a splash screen once 2314 is done
  • Known Unknowns

    Development Estimate
    • How will the order weight interact? Requires API.
  • QA: snapshot | local | testing | other

    • Routing in tab group is non-trivial 
    • Drag and drop accessibility (existing handle should be fine for tabbing), will need custom keyboard management
  • QA: snapshot 

  • Development Estimate: 5d

    • expecting to carry over into Sprint 149


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions








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 = 1363 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 = 1363
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy
serverSystem Jira
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 = 1363
serverId01505d01-b853-3c2e-90f1-ee9b165564fc