Versions Compared

Key

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

Sprint Goal / Focus 

Sprint Schedule

  • Sprint: 158
  • Release: 2023.1 Orchid  
    • Sprint 8 of 8 since Release Development Cycle Starts (Sprint 151) to Feature Freeze (Sprint 158)
    • Sprint 159: Module Release Deadline [FOLREL-565]
      • Backend 22 Feb 2023
      • Frontend 24 Feb 2023
    • Sprint 162: Bugfix Release Deadline (31 Mar 2023) [FOLREL-581]

Development Meetings

  • 1 Feb 2023
  • 6 Feb (Mid Sprint Review)
  • 15 Feb

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Jag: OOO week 2

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

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3732

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2612

  • Triage: NA

  • Approach
    • Backend
      • add new refdata set for new contentType, called, eg SubscriptionAgreementContentType to keep separate from ContentType
      • Set SubscriptionAgreementContentType 
      • based on new set of refdata, set up domain class, grails view and migration (but not schema)
        • see PR on ERM-2045
        • use curl/postman to attempt to bind contentType to determine whether internal or external
      • uses existing mechanisms for refData and contentType handling mechanisms
      • may need to bump migration number if dropping tenant doesn't just work
    • Frontend
      • set up multi-selection on agreement as per existing patterns
      • add new filter option according to existing patterns
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: mod-agreements

  • Tests / Data / Dependencies: 

    • update frontend tests, no backend tests needed
  • Known Unknowns: none

  • QA: snapshot

  • Release Target: Orchid
  • Development Estimate: Wed/Thu




No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2474

  • Triage

    • Attempt to reproduce this on non-GBV environment
    • Review what is and isn't being populated
      • additional_info is added
      • title is not the expected title (compare wit title in message)
    • Possible that additionalInfo is only updated at certain times?
    • Check whether error log has similar info
    • Disconnect between what and how we are appending, using special Grails sauce
      • error and info not updated together
      • possible race condition
  • Approach
    • potentially extend with titleId
  • Components and Changes

    • Frontend: NA

    • Backend: mod-agreements

  • Tests / Data / Dependencies: 

    • Owen to set up testdata as a json package with errors
  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Orchid
  • Development Estimate: needs triage and re-learning: review on Wed

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2622

For QA

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2621

For QA

Release Tasks (Orchid)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Release Tasks (Morning Glory Hotfix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Release Tasks (Nolana Hotfix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA




Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions


Add test to stripes-kint-components to check encoding of special characters

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2626

Ethan Freestone 
  1. Set up Jira issue
  2. Set up cypress end-to-end test for agreements (Ethan)
    1. check it exists in navbar, and that it shows up 
    2. work out how to run it
    3. use as template for extending within agreements
  3. Export Testrails list (Owen)
  4. Review for e2e conversion (team)
  5. Get Testrails logins (Jag)

Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2624
 

Add new view-only permission to package.json, based on 

Code Block
 {
        "permissionName": "settings.agreements.enabled",
        "displayName": "Settings (Agreements): Can view and edit settings",
        "subPermissions": [
          "module.agreements.enabled",
          "settings.enabled",
           "configuration.entries.collection.get",
          "configuration.entries.item.put",
          "configuration.entries.item.post"
        ]
      },

But without 
"configuration.entries.item.put",
"configuration.entries.item.post"

and will need also

"erm.custprops.view",

"erm.refdata.view"

No need to worry about export.

Reflect same structure in read only permissions as in manage permissions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2625


Add new view-only permission to package.json, based on 

Code Block
 {
        "permissionName": "settings.licenses.enabled",
        "displayName": "Settings (Licenses): Can view and edit settings",
        "subPermissions": [
          "module.licenses.enabled",
          "settings.enabled",
           "configuration.entries.collection.get",
          "configuration.entries.item.put",
          "configuration.entries.item.post"
        ]
      },

But without 
"configuration.entries.item.put",
"configuration.entries.item.post"

No need to worry about export.

Reflect same structure in read only permissions as in manage permissions




Rolled Over From Previous Sprint


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

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions






Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2550

To close

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2488

(question)
  • Triage

    • useEffect doing job of mount handler
  • Approach
    • can input approach be set up differently?
    • is only one id needed, in which case how would stripes handle this across tabs?
    • persistent results wiped across app-tab switching
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

    • unknown impacts
  • QA: snapshot | local | testing | other

  • Development Estimate





Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2549

(error)Defer until Nolana Hot Fix environment is ready. 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3884

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2610
/
Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2611

  • Work to do UUID is done and verified on a new deployment, but not an existing one, for regression testing
  • Needs
    • deployment of old code
    • successful harvest
    • deployment of new code
    • delta harvest
  • Not clear whether the k-int environment is able to support this regression testing
    • Owen to check with Ian for future utility
  • For now, to be tested by screensharing with Ethan on Thu morning


For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2474




For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2547

Requires Testrail scripts


Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2449






Sprint Summary

ERM

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels != release and labels in (licenses, agreements, erm) and Sprint = 1517 and issuetype in standardIssueTypes()
serverId6ccf3fe4-3301-368a-983e-20c466b11a49


Dashboard

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels = dashboard and Sprint = 1517
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Other

Jira
serverFOLIO Issue Tracker
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 = 1517
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

No Label

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels is empty and Sprint = 1517
serverId6ccf3fe4-3301-368a-983e-20c466b11a49