Page Comparison

This page contains historical data from the Overall Status Update table on the FOLIO Q4 2019 (Edelweiss) Weekly Status Report

...

Report Date

...

Overall Status Update

...

Q1 Feature Count on Report Date

...

Status Report

Report Date

Overall Status Update

Q1 Feature Count on Report Date

Functional

NFR

2019-12-17

Jakub Skoczen

Started sprint 79 – a 4 week sprint
Q4 release:
- Q4 release branch is being updated with Q4 bugfix releases – https://github.com/folio-org/platform-complete/tree/q4-2019
- All modules have been released for Q4 (at least once)
- Release management spreadsheet: https://docs.google.com/spreadsheets/d/11ciGyodrIX_NxjZmBYfDAp9mjfKcL_LSG32Qn-H0nkM/edit#gid=0
- mod-inventory-storage will have a new "feature" release – 18.2.0 to include the HRID changes
Platform Dev updates:
- In support of Q4 functionals and defects:
  - RMB 29.1.2 released with additional bugfixes (RMB-533):
  - RMB 29.2.0 release in the works:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    enabler for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-498
    fix for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-379
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-390
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-395
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-536
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-537
- Performance-related:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
    to help addressing various perf issues, specifically in authn/z subsystem
Platform DevOps updates:
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2268
  is DONE which effectively completes development work on
  Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2401
  to create a screencast with a demonstration of FOLIO-2268
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirements

Cate Boerema (Deactivated)

Core functional is still planning for Sprint 79 (despite the
- Team has picked up one of Holly's Fee/Fine features
  Jira Legacy
  server System JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-390
- Since this is a new area, there is a lot to discuss and team would like to be sure they have all questions answered given folks will be out over the holiday
- Will allocate 40% of story points to bug fixing
  - New process will ask teams to dedicate 40 - 50 % of story points to bug fixing until all p1, p2 and p3 bugs are closed. Vega, Concorde and Folijet will also help work through the Core Functional bug backlog
  - Focus to start would be ui-only fixes as back-end bugs are more involved (often require architecture decisions, are breaking changes etc) and the defect priorities need to be reconsidered for back-end bugs
Cap planning team working to get initial Q1 planning together by end of week
Features being redistributed across teams

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-12-17) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-12-17) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-12-10

Jakub Skoczen

Mid sprint 78
Q4 release:
- Q4 release branch has been created on Monday – https://github.com/folio-org/platform-complete/tree/q4-2019
- A group of modules didn't meet the December 4th deadline which means that verifying and branching was delayed until Monday morning. Most of them has been released until Monday morning and are included in Q4 but 3 modules had to be removed to allow for the release succeed: mod-patron, edge-patron, edge-sip2. These will be included in the coming days.
- Release management spreadsheet: https://docs.google.com/spreadsheets/d/11ciGyodrIX_NxjZmBYfDAp9mjfKcL_LSG32Qn-H0nkM/edit#gid=0
Platform Dev updates:
- In support of Q4 functionals and defects:
  - RMB 29.1.1 released with additional bugfixes (RMB-532):
  - RMB 29.2.0 awaits:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    enabler for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-498
    fix for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-379
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-390
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-395
- Performance-related issues:
- - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-407
    added to the sprint
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-408
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
    to help addressing various perf issues, specifically in authn/z subsystem
Platform DevOps updates:
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  PR previews builds are being rolled out, some problems remain:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
    temporarilay on hold while preparing Q4
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2366
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2358
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirements

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-12-10) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-12-10) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-12-03

Jakub Skoczen

Mid sprint 78
Q4 release:
- Q4 release branch has been created on Monday – https://github.com/folio-org/platform-complete/tree/q4-2019
- A group of modules didn't meet the December 4th deadline which means that verifying and branching was delayed until Monday morning. Most of them has been released until Monday morning and are included in Q4 but 3 modules had to be removed to allow for the release succeed: mod-patron, edge-patron, edge-sip2. These will be included in the coming days.
- Release management spreadsheet: https://docs.google.com/spreadsheets/d/11ciGyodrIX_NxjZmBYfDAp9mjfKcL_LSG32Qn-H0nkM/edit#gid=0
Platform Dev updates:
- In support of Q4 functionals and defects:
  - RMB 29.1.1 released with additional bugfixes (RMB-532):
  - RMB 29.2.0 awaits:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    enabler for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-498
    fix for
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-379
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-390
    
    Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-395
- Performance-related issues:
- - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-407
    added to the sprint
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-408
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
    to help addressing various perf issues, specifically in authn/z subsystem
Platform DevOps updates:
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  PR previews builds are being rolled out, some problems remain:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
    temporarilay on hold while preparing Q4
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336
- Jira Legacy
  server System JIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2366
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2358
  - Jira Legacy
    server System JIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirements

Cate Boerema (Deactivated)

Last day before module release deadline for Q4
Overall feeling is a bit calmer this quarter than last when we had many PRs arrive at the last minute and too few people reviewing
Currently there are only 14 must-fix stories and bugs still outstanding (see dashboard: https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=10900)
I am sure more will be added once BugFest gets going
We have until December 18th for bug fixing
Core functional:
- Jira Legacy
  server System JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-2114
  was (somewhat unexpectedly) completed in time for the Q4 release!
- Jira Legacy
  server System JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1727
  was also pulled into the quarter and completed (this was low hanging fruit and a high priority for Chalmers)
- Jira Legacy
  server System JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1626
  was not completed and had to be split to create 4 spillover features. Some of these may not be a top priority for MVP:
  - UXPROD-2170 Store Effective Copy Number
  - UXPROD-2171 Store Effective Call Number Type
  - UXPROD-2172 Call Number Accordion on Item Record
  - UXPROD-2173 Display Effective Call Number Throughout Requests App
POs will be adding priorities to their spillover MVP features. Higher priority features are those that would require more testing and training (assumption is that those should be completed first)
Capacity planning group will synthesize this PO priority data and the updated team allocations to generate a plan for Q1

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-12-03) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-12-03) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-11-26

Jakub Skoczen

Mid-sprint 77
Platform Dev updates:
- In support of Q4 functionals and defects:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    enabler for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-498
    fix for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-379
    
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-390
    
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-395
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-56
    fix for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIU-1324
- Performance-related issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-506
    to address various search performance issues, including
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-256
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
    to address various perf issues, specifically in authn/z subsystem
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-51
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-353
  completed
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-349
  completed
Platform DevOps updates:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
    remaining work is related to automatically assigning "version" number to preview artifacts.
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2336
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2315
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirement
Q4 release:
- December 4th is the module release deadline
- Release management spreadsheet: https://docs.google.com/spreadsheets/d/11ciGyodrIX_NxjZmBYfDAp9mjfKcL_LSG32Qn-H0nkM/edit#gid=0

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-11-26) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-11-26) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-11-19

Jakub Skoczen

Started sprint 77
Platform Dev updates:
- In support of Q4 functionals and defects:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    enabler for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-498
    fix for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-379
    
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-390
    
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-395
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-56
    fix for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIU-1324
- Performance-related issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-506
    to address various search performance issues, including
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-256
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
    to address various perf issues, specifically in authn/z subsystem
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-51
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-353
  completed
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-349
  completed
Platform DevOps updates:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
    remaining work is related to automatically assigning "version" number to preview artifacts
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2315
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirement
Q4 release:
- December 4th is the module release deadline

Cate Boerema (Deactivated)

Started last sprint of Q4 development
Prioritizing wrapping up development on in progress features and priority bug fixes
There will be significant spillover (52 issues currently - see table on Q4 2019 Dashboard)
In addition to features that will spill over in their entirety, many In progress features will have to be "split" meaning there will be partial carry-over
For Core Functional, the following features: will need to be split:
- Jira Legacy
  server System JiraJIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1626
- Jira Legacy
  server System JiraJIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-140
- Jira Legacy
  server System JiraJIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1893
- Jira Legacy
  server System JiraJIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-2114
Many (most?) features currently "In progress" are likely to need to be split.
- In some cases, a good thin thread has been implemented in Q4 and what is left is lower priority and/or small in scope
- In other cases, a sizeable amount of priority development will need to be split and carried over.
- Often the remaining development can be completed in the Q4 development period (just too late to make the actual release)
The cap planning group is:
- Evaluating the items that have been tagged by POs as spillover to see which are the highest priority for the 2020 cohort (including Chalmers). Holly is following up with POs on features that don't have high implementer rankings to better understand their priority. These usually have explanations e.g. they represent thin thread workarounds for other features the implementers really need.
- Gathering info on what the development capacity will be in Q1

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-11-19) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-11-19) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-11-12

Cate Boerema (Deactivated)

Second week of second to last development sprint
Core functional:
- Still struggling with
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-357
  . This feature (
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1626
  ) has taken all quarter and was estimated at 3 days FE/3 days BE
- Finally got first story for
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-2114
  into Code Review and picked up the next one
- UI developers are working through many Inventory search and filter enhancements, wrapping up Reorder request queue feature and fixing priority bugs (also struggling with integration tests)
Overall, currently we have 47 features that have been tagged as likely spillover from Q4 (see dashboard: https://issuesfolio-org.folioatlassian.orgnet/secure/Dashboard.jspa?selectPageId=10801)
- Cap planning team beginning to look at what's there and the capacity for Q1 so we can plan
Chalmers continues to uncover issues with operational impact such as:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CIRC-543
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-145
  will be hotfixed when ready
- needs to be fixed for Q4
  - This issue results from the fact that barcode data isn't synched between Users and Requests
  - We have the same problem with items and requests and are waiting for pub-sub for a complete resolution to this issue
  - In the meantime, we can fix the linking issue with a simple change to how filtering works

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-11-12) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-11-12) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-11-05

Jakub Skoczen

Started sprint 75
Platform Q3.2 updates (dev):
- Performance-related issues:
  - Ongoing optimisation work in the authn/z subsystem
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-51
    , specifically:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key OKAPI-770
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2296
    to help investigate perf problems going forward
  - Pending perf problems to be addressed by other teams:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODNOTIFY-54
  - Other perf issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-497
    to allow for estimating hitcount and address perf issues like
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-256
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1820
  New development work (RMB 28.x related):
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-349
    has been completed (in PR) to allow the Functional team to complete
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-564
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-499
    to allow addressing
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-647
- Batch import APIs for Inventory:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-353
Platform Q3.2 updates (devops):
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  pending completion on the following tasks:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2303
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2298
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2315
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirement
Q3.2 (Daisy) release:
- Hotfix release issues: (label ^q3.2-2019-hotfix^):
- Jira Legacy
  server System JiraJIRA
  jqlQuery labels = q3.2-2019-hotfix
  count true
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

Cate Boerema (Deactivated)

Started sprint 76 on Monday - 2 sprints left until module release deadline!
- Some Core Functional features have been slow-going this quarter because they are things we haven't done before (e.g.
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key MODINVSTOR-348
  ,
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1626
  (which had to be implemented differently than the effective location) and
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1626
  )
- The team feels we are close to getting being over the hump, at which time development should accelerate
- Core Functional folks had a good meeting last week with Jakub to discuss plans for Inventory search and filter and we have a clear plan for some long-awaited features such as:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1685
    - Now assigned to Core Platform for Q4
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-724
    - Which will allow searching by CQL with plans to later implement
    Jira Legacy
    server System JiraJIRA
    columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1941
    to improve user experience with query validation and potentially reduce performance and stability issues due to bad inputs. I see this feature is currently marked Q4 2019 for Core Platform. Is that right?
- Two disruptive requests bugs were fixed and pushed to Chalmers as a hotfix this week:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-516
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKOUT-553
  - The number of mysterious circulation issues being reported by Chalmers has virtually stopped
- It looks like there will be more spillover features this quarter than we have seen in the past and the PO have gathered their thoughts on why that may be. Issues include team turnover and vacations, dependencies between features, underestimated features and late requirements.
- POs and Anton discussed the desire to capture bug reports from broader community, as implementers are beginning to test in earnest. Currently thinking about setting up a special project for this purpose. More conversations are needed and we've submitted as a topic for Wolfcon.

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-11-05) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-11-05) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-10-22

Jakub Skoczen

Started sprint 75
Platform Q3.2 updates (dev):
- Security-related:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODPERMS-68
- Performance-related issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKOUT-542
    CLOSED.
  - The Platform team will continue investigate perf optimisation of the authn/z subsystem through:
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-51
    , specifically:
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-770
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2296
    to help investigate perf problems
  - Pending perf problems to be addressed by other teams:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODNOTIFY-54
  - Other perf issues:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      still shows performance issues after RMB-468 updates, which seems to be related to reporting hit counts
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UXPROD-1820
  New development work (RMB 28.x related):
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODINVSTOR-349
    enabler for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-564
    is going to be addressed this week
Platform Q3.2 updates (devops):
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  pending completion on the following tasks:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2303
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2298
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2280
    related to reference env security, BLOCKED on tasks to upgrade permission handling on individual modules
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirement
Q3.2 (Daisy) release:
- Hotfix release issues: (label ^q3.2-2019-hotfix^):
- Jira Legacy
  server System JiraJIRA
  jqlQuery labels = q3.2-2019-hotfix
  count true
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

Cate Boerema (Deactivated)

Chalmers is reporting lots of "items out of place" type issues such as:
- Items that are showing up on the Hold shelf clearance report for one circ desk but aren't on the hold shelf. These are sometimes found awaiting pickup on other service points or sometimes found.
- Requests that are Closed - Filled with no evidence of a loan for that item for the requester
- Etc
Most of these are being reported via Slack channel and investigated by Cate
- These are often difficult to debug - some observations from Chalmers can no longer be reproduced when checked (e.g. item no longer on Hold shelf clearance report or item status has changed)
- Some are reproducable and bugs have been filed such as:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CHAL-85
    and
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-516
    will need to be hotfixed when complete
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UIIN-806
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CHAL-87
Lots of Q4 work in progress but a significant number of features are at risk as they have been delayed and/or haven't started
- Cap planning team will meet on Friday to discuss features likely to spillover
- Cate will ask POs to tag items at risk

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-10-22) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-10-22) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-10-15

Jakub Skoczen

Mid sprint 74
Platform Q3.2 updates (dev):
- Security-related issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-766
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-762
- Performance-related issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    IN REVIEW. Cate mentioned that she saw a visible improvement after the applying the latest round of hotfix releases. If the improvement is sufficient the issue can be closed. Similarly,
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKOUT-542
    may be reviewed again to verify if there's an improvement. The Platform team will continue perf optimisation of the authn/z subsystem through:
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key MODAT-51
  - Pending perf problems to be addressed by other teams:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODNOTIFY-54
  - Next in-line, Platform team will work to reproduce check-in/check-out perf issues on the perf testing env:
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key CIRC-466
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1820
    New development work (RMB 27.x related) has been resumed this week:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      pending verification (on hold due to dev vacation)
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-349
      enabler for
      Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key UIIN-564
      is nearing completion
Platform Q3.2 updates (devops):
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  pending completion on the following tasks:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2303
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2298
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2280
    related to reference env security
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2218
    related to scaling issues caused by the increased CI/CD requirement
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2242
    related to the new model for configuring memory requirements of individual modules
Q3.2 (Daisy) release:
- Hotfix release issues: (label ^q3.2-2019-hotfix^):
- Jira Legacy
  server System JiraJIRA
  jqlQuery labels = q3.2-2019-hotfix
  count true
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

Cate Boerema (Deactivated)

Testing hotfixes for Chalmers issues:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-49
  - Hotfix has been applied to BF3.1 but it is difficult to test due to the below issues not yet being addressed. Will finish testing when those fixes have been applied.
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-54
  - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key CHAL-52
  - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-79
seems to have been addressed (cant repro in any local environments). Need to decide if we want to hotfix to Chalmers for 3.1 or if they can wait for the upgrade next week
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-43
Waiting for "refined design" from Filip
Writing additional stories for
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-113
as we have determined we need to introduce a new item and request status (this entails a significant amount of additional work)
Charlotte has supplied many new Inventory search and filter stories for the Core Functional team as part of
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UXPROD-140
. Development will support searching and filtering by item and holding data but results are always instances (for now): https://docs.google.com/presentation/d/1HUX9ed0Qnx2jRE6M4DRlfTFUa-MUPJICD9k5lPECqew/edit#slide=id.g5dc4a09ded_0_0
Ann-Marie has written a number of stories for HRID handling across SRS, Batch import, Inventory and MARCcat:
- UXPROD-2114 for Inventory/Core-Fxn
- UXPROD-2115 for SRS/Folijet
- UXPROD-2116 for MARCcat/AtCult

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-10-15) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-10-15) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-10-08

Started sprint 74
Platform Q3.2 updates (dev):
- Chalmers-related performance and stability issues:
  - mod-authtoken 2.3.0 and mod-permissions 5.8.3 released with performance improvement, available for both Q3.1 and Q3.2. Brings overall request time improvements, incl. Check-in/Check-out. To be verified on Bugfest environments when hotfixes are installed there.
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    back in OPEN for another review. Additional, tasks ongoing
  - - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-51
      reports ~35% request time spent in mod-authtoken/mod-permissions for a warm system with new improvements. Depending on trhe bugfest envs numbers, Platform team will look at additional improvements.
    - Problems to be addressed by other teams are still incomplete:
      - Jira Legacy
        server System JiraJIRA
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODNOTIFY-54
    - The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:
      Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-466
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1820
    New development work (RMB 27.x related) has been resumed this week:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      pending verification
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-349
      enabler for
      Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key UIIN-564
      is back in development
Platform Q3.2 updates (devops):
- Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  which consists of the following sub-tasks:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2275
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2265
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2267
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2060
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2276
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2282
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2237
Q3.2 (Daisy) release:
- Daisy out on 2nd October
- Remaining problems will be addressed through hotfix releases. Jira tickets that should be addressed through hotfix releases will be labelled as ^q3.2-2019-hotfix^
- Jira Legacy
  server System JiraJIRA
  jqlQuery labels = q3.2-2019-hotfix
  count true
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
- Proposal for Q3.2 bugfix/support release cycle:
  - continue publishing bugfix releases for issues tagged as ^q3.2-2019-hotfix^ until and including Jan 2020 (one month after Q4 is out)
- What about Q3.1 bugfixes?
- release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

Nearly ready to hotfix 3.1 for Chalmers to address issues with Loans page when there are >100 loans
Matt Reno is working on another hotfix-worthy bug:
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-49
Filip is helping us to design a solution for
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key CHAL-43
Review has been conducted of Tod Olsen's call number normalization code and it looks like FOLIO will be able to reuse it (may need a few adjustments first)
Otherwise, teams are progressing on Q4 MVP features and POs continue to write stories and ready the backlog

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-10-08) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-10-08) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

2019-10-01

Mid Sprint 73
Platform Q3.2 updates (dev):
- Various security-related issues brought up last week took precedence over other work:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-763
    solution for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2287
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key OKAPI-764
    solution for
    Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2286
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key RMB-478
- Chalmers-related performance and stability issues:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UICHKIN-111
    all individual backend tickets have been addressed (for list see previous report) besides:
  - - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODAT-51
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODPERMS-67
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODUSERS-150
    - Problems to be addressed by other teams are still incomplete:
      - Jira Legacy
        server System JiraJIRA
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODSOURCE-76
      - Jira Legacy
        server System JiraJIRA
        serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
        key MODNOTIFY-54
    - The ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:
      Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key CIRC-466
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key UXPROD-1820
    New development work (RMB 27.x related) has been resumed this week:
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-256
      pending verification
    - Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key MODINVSTOR-349
      enabler for
      Jira Legacy
      server System JiraJIRA
      serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
      key UIIN-564
      is back in development
Platform Q3.2 updates (devops):
- Standard release related activities have been completed last week (what remain is ad-hoc hotfix releases) and the team has resumed focus on Continuous Deployment work, namely:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key FOLIO-2227
  which consists of the following sub-tasks:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2275
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2265
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2267
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2268
- Additionally the following CI problems are being addressed:
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2060
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2276
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2282
  - Jira Legacy
    server System JiraJIRA
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key FOLIO-2237
Q3.2 (Daisy) release:
- release pending on a bugfix for
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIU-1271
  which should be available related today
- during
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key UIU-1271
  another problem has been discovered,
  Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key STCOR-392
  , will be addressed by a Stripes bugfix release after Q3.2
- Bugfix release cycle for Q3.1, Q3.2 and preview release for Q4 should be established ASAP. Currently it's not clear for how long we'd like to support Q3.1 (and going forward Q3.2) and release bugfixes. Proposal:
  - end-of-life Q3.1 asap – e.g mid-October (depends on Chalmers upgrade plans)
  - continue publishing bugfix releases (critical defects only) for Q3.2 until and including Jan 2020
- release spreadsheet: https://docs.google.com/spreadsheets/d/1DKV8rf3kD7QAz57etqA-C2FqHHLZmRVmMZFobvDszn8/edit#gid=0

Cate Boerema (Deactivated)

Chalmers is live!
Bugs and enhancement requests are beginning to come in:
Jira Legacy
server System JiraJIRA
jqlQuery filter=11808
count true
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Have created first pass at release notes accessible from here: Cross Release NotesStatistics
Q3 needs to be wrapped up in JIRA. There are still ~10 open UXPRODs

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND (labels != NFR OR labels = EMPTY) AND fixVersion was "Q4 2019" ON (2019-10-01) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Jira Legacy

server	System JiraJIRA
jqlQuery	project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019" ON (2019-10-01) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
count	true
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

...

Versions Compared

Old Version 6

New Version Current

Key