Skip to end of metadata
Go to start of metadata

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

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

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

  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: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

UXPROD-3754 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2332 - Getting issue details... STATUS

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

UXPROD-3776 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2333 - Getting issue details... STATUS

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

UXPROD-3116 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2334 - Getting issue details... STATUS

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

UXPROD-3756 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2330 - Getting issue details... STATUS

(question)
  • Approach

    • keep flat route to support easy migration in future: no change except to where (not what) stuff is displayed
    • read header url
      • if in Agreements or Agreements Line > Agreement Search
      • if in eResources or LocalKB Search > eResource Search (defaulting as normal)
    • this also determines what the primary is
  • Components and Changes

    • Frontend: ui-agreements

    • Backend

  • Tests / Data / Dependencies / Known Unknowns: NA

  • QA: snapshot

  • Development Estimate: <1d

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

ERM-2337 - Getting issue details... STATUS

  • Approach

    • normally happens when a field is missing the  name
    • possibly a KiwtFieldArray / finalForm issue
    • reproduce locally for better stacktrace
    • if not, check snapshot is up to date
  • Components and Changes

    • Frontend: ui-erm-comparison, comparison.fieldArray

    • Backend: none

  • Tests / Data: NA

  • Dependencies: NA

  • Known Unknowns

  • QA: snapshot | local 

  • Development Estimate: ??

ERM-2338 - Getting issue details... STATUS

  • Approach

    • AL type options are not from the same field, but constructed, in a way that it could 
  • Components and Changes

    • Frontend: ui-agreements, AgreementLineFilters (or one step above)

    • Backend: none

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot 

  • Development Estimate: ??

ERM-2340 - Getting issue details... STATUS

(tick)
  • Approach

    • Filter is gone, but option is not cleared from display and not removable
    • Logic to display is separate to lookup logic
    • Throws up an issue with the 
    • Preferably clear if not set (ie if URL is clear).  If not, intercept Reset All and clear all. 
    • Need to check for looping behaviour
  • Components and Changes

    • Frontend: 

    • Backend: none

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate: ??

ERM-2341 - Getting issue details... STATUS

(question)Owen to re-check and confirm to close as Won't Do, as behaviour is currently to show a single confirmation modal after all deletion choices are mode. 

ERM-2345 - Getting issue details... STATUS

(tick)

ERM-2335 - Getting issue details... STATUS

Claudia Malzer 
  • Approach

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot 

  • Development Estimate

ERM-2339 - Getting issue details... STATUS

  • Approach

    • query parameters will include sort
    • inspect query object handed by sasquery (or, preferably kiwt
    • if it includes filter/terms, enable initial query - add enabled prop to the useInfiniteFetch (or useBatchedFetch or useQuery) options parameter (in ALroute - see line 53-54) 
    • if not, do not enable infiniteFetch (enabled = filter settings; line 77)
    • when isIdle is returned from query, show the prompt to select a filter
  • Components and Changes

    • Frontend: ui-agreements (agreementLineRoute)

    • Backend: none

  • Tests / Data /

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

ERM-2336 - Getting issue details... STATUS

  • Approach

    • Expected
      • if no other filters, should set to default filters
      • if default, clear filters
    • may be state-driven, in which case it needs to be url-driven
      • ie, remove custom logic
      • (search and sort query will handle defaults as expected)
    • Check impacts on other filters
  • Components and Changes

    • Frontend: ui-agreements

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Removed

Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3754 - Getting issue details... STATUS

ERM-2307 - Getting issue details... STATUS

(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

UXPROD-3754 - Getting issue details... STATUS

ERM-2310 - Getting issue details... STATUS

(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





Issue ID

Deferred to

Notes / Estimates / Actions







Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

Rolled Over From Previous Sprint

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3754 - Getting issue details... STATUS

ERM-2288 - Getting issue details... STATUS

  • Current State: 
  • TODO
    • fix removeFrom error
      • replace `it.contentTypes` with `it`
        • doesn't throw an error, but also doesn't make change in db
    • fix each-iterator error
      • ensure happening within transaction
      • attempt to save without flushing, to avoid trying something new
    • re-test
    • confer with Steve/Ethan if more needed
  • Development Estimate: ? 

UXPROD-3116 - Getting issue details... STATUS

ERM-2313 - Getting issue details... STATUS

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

ERM-2315 - Getting issue details... STATUS

  • Current State
    • 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

UXPROD-3754 - Getting issue details... STATUS

ERM-2311 - Getting issue details... STATUS
  • 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

UXPROD-3754 - Getting issue details... STATUS

ERM-2308 - Getting issue details... STATUS

  • 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: 

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

  • Development Estimate: == ERM-2311

UXPROD-3754 - Getting issue details... STATUS

ERM-2309 - Getting issue details... STATUS

  • Approach

    • add accordian to package filters (Availability Constraints)
    • show list similiar to Tags  / External Source Data
    • use multiselect rather than checkboxes doing lookup
      • 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

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2214 - Getting issue details... STATUS

(error)

Pending Dependency: ERM-2316. 

Moved to Sprint 149 to coincide with ERM-2316

In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

ERM-1343 - Getting issue details... STATUS

ERM-2234 - Getting issue details... STATUS Can regression test a single field array (such as alternateNames)

UXPROD-3591 - Getting issue details... STATUS

ERM-2093 - Getting issue details... STATUS

Identifier array populated with empty objects

STSMACOM-678 - Getting issue details... STATUS

ERM-2220 - Getting issue details... STATUS



ERM-2278 - Getting issue details... STATUS

Regression test use of plugin in ERM Comparison, dashboard and new agreement line search

ERM-2279 - Getting issue details... STATUS


UXPROD-3756 - Getting issue details... STATUS

ERM-2289 - Getting issue details... STATUS

Will be significant QA / UAT effort

Usergroup discussion this week

UXPROD-3754 - Getting issue details... STATUS

ERM-2306 - Getting issue details... STATUS

Can QA with JSON and provide file for ERM-2308/ERM-2309

UXPROD-3116 - Getting issue details... STATUS

ERM-2312 - Getting issue details... STATUS

Can regression test, but not migration from one to another model 9which has been dev tested). 


For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3116 - Getting issue details... STATUS

ERM-2314 - Getting issue details... STATUS

  • 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

    • How will the order weight interact? Requires API.
    • 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

Key Summary T Assignee Status Component/s
Loading...
Refresh


Dashboard

Key Summary T Assignee Status Component/s
Loading...
Refresh

Other

Key Summary T Assignee Status Component/s Labels
Loading...
Refresh

Not Labeled

Key Summary T Assignee Status Component/s
Loading...
Refresh