Versions Compared

Version Old Version 1 New Version Current
Changes made by

Cate Boerema (Deactivated)

Cate Boerema (Deactivated)

Saved on

Key

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

...

  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyRMB-506
     to address various search performance issues, including 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-256
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyOKAPI-770
     to address various perf issues, specifically in authn/z subsystem 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODAT-51

...

This page contains historical data from the Overall Status Update table on the FOLIO Q1 2020 (Fameflower) Weekly Status Report

...

Report Date

...

Overall Status Update

...

Q1 Feature Count on Report Date

...

Jakub Skoczen

...

  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyRMB-499
     enabler for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-647
     
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyRMB-498
     fix for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-379
     
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-390
     
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-395
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODAT-56
      fix for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIU-1324

This page contains historical data from the Overall Status Update table on the FOLIO Q1 2020 (Fameflower) Weekly Status Report


Report Date

Overall Status Update

Q1 Feature Count on Report Date



FunctionalNFR
2020-04-02

Jakub Skoczen

  • Q1 2020 Release Management
    • Release environment: https://folio-fameflower.dev.folio.org/
    • https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8/edit#gid=0
    • Bugfix releases since last report:
      • ui-erm-usage 2.7.1
      • data-import-processing-core v1.0.1
      • mod-inventory-storage 19.1.1
      • mod-source-record-storage v3.1.2
      • stripes-erm-components 2.3.1
      • ui-licenses 3.7.2
      • mod-data-import-converter-storage v1.7.1
      • stripes-acq-components v2.0.2
      • ui-invoice v2.0.2
      • ui-receiving v1.0.1
      • ui-organizations v2.0.1
      • mod-organizations-storage v3.0.1
      • mod-source-record-manager v2.1.1
      • mod-pubsub v1.1.1
      • mod-inventory 14.1.0
      • od-orders-storage v10.0.1
      • ui-orders v2.0.1
      • ui-data-import v1.8.1
      • mod-circulation 18.0.1
      • mod-invoice-storage 3.1.1
      • mod-erm-usage-harvester 1.6.1
      • mod-licenses v2.1.1
      • mod-finance 2.0.1
      • mod-ncip v1.1.0
      • edge-ncip v1.2.0
      • mod-data-export 1.1.0 
  • Core Platform development  in Sprint 84
    • Hit count issues reported during bugfest: 
      Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      MODINVSTOR
      RMB-
      353 completed
      591
       
    • RMB 29.4.0: released feature back-port for Edelweiss:
      • Jira Legacy
        serverSystem
      Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
      MODINVSTOR
      • RMB-
      349 completed
    Platform DevOps updates:
      • 575
         blocker for 
        Jira Legacy
        serverSystem
      Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
      FOLIO
      • MODINVSTOR-
      2227 PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed
      • 413
    • RMB 29.5.0 (master), IN DEVELOPMENT:
      • Jira Legacy
        serverSystem
        Jira remaining work is related to automatically assigning "version" number to preview artifacts.
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
FOLIO-2268
RMB-588
  • Jira Legacy
    serverSystem
    • Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
    FOLIO
    • RMB-
    2336Additionally the following CI problems are being addressed
    • 164
  • Okapi 2.38.0 released with the following performance fixes:
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyFOLIO-2315OKAPI-813
       reported by Martin Tran, related:
  •  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
        serverSystem
      Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
      FOLIO-2218 related to scaling issues caused by the increased CI/CD requirement
    • Q4 release:
        • OKAPI-817
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-818
      • Jira Legacy
        serverSystem
    JirajqlQueryproject = 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 counttrue
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-811
           reported by Wayne Schneider, related:
          • Jira Legacy
            serverSystem JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            keyOKAPI-820
          • Jira Legacy
            serverSystem
    JirajqlQueryproject = uxprod AND type = "new feature" AND
          • JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            keyOKAPI-821
      • Automatic Migrations / Module Upgrade  related:
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-804

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = 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 2019Q1 2020" ON (20192020-1104-2602) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    2019-11-19

    Jakub Skoczen

  • Started sprint 77
    • Platform Dev updates:In support of Q4 functionals and defects:  Jira LegacyserverSystem Jira

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-04-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyRMB-499 enabler for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-647
     
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyRMB-498
     fix for 
    2020-03-26

    Jakub Skoczen

    • Core Platform development  in Sprint 84
      • RMB 29.3.2: released
        • Julian working on mod-inventory-storage 19.1.1  with RMB 29.3.2 and optimized upgrade path for Edelweiss → Fameflower
      • RMB 29.4.0 (branch) feature backport for Edelweiss:
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODINVSTORRMB-379575
            blocker for 
          Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODINVSTOR-390
           
          413
      • RMB 29.5.0 (master), IN DEVELOPMENT:
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODINVSTORRMB-395588
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODATRMB-56
            fix for 
          164
    • Automatic Migrations / Module Upgrade  related:
      • Jira Legacy
        serverSystem
        JiraPerformance-related issues:
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UIU-1324
        OKAPI-773
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        RMB
        OKAPI-
        506 to address various search performance issues, including 
        804
    • Performance related:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-256
        OKAPI-813
         memory leak reported by Martin Tran, heap dumps delivered from the "no dropwizard" branch are invalid, Martin has been asked to repeat tests
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyOKAPI-
        770 to address various perf issues, specifically in authn/z subsystem 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODAT-51
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINVSTOR-353
         completed
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINVSTOR-349
         completed
      Platform DevOps updates:
      • Jira Legacy
        serverSystem Jira811
         reported by Wayne Schneider

    Cate Boerema (Deactivated)

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = 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 "Q1 2020" ON (2020-03-26) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2227 PR previews builds are being tested by the Platform DevOps, only one task remains open and it's been partially completed:

    Jira Legacy
    serverSystem

    Jira

    JIRA

    serverId

    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-03-26) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2268 remaining work is related to automatically assigning "version" number to preview artifacts
  • Additionally the following CI problems are being addressed:
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyFOLIO-2315
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyFOLIO-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
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-1626
  • Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-140
    • Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

    2020-03-17

    Jakub Skoczen

    counttrue
    • Q1 2020 Release Management
      • Platform team handled mod-user-import and mod-login-saml upgrades to RMB 29.x and  Q1 releases.
      • Release candidate env not bootstrapped due to missing module releases.
      • https://docs.google.com/spreadsheets/d/1NvvCq1wTfDeCnd7zHDIzLI7RBfuSr_Ty0tbzYzgEaI8/edit#gid=0

      • platform-core: Missing/unannounced module releases as of Monday 3/16 according to the release spreadsheet (maintainers and POs notified):

        • VEGA : mod-calendar, mod-email, mod-event-config, mod-feesfines, mod-template-engine, mod-sender, ui-calendar, ui-checkin, ui-circulation, ui-myprofile, ui-plugin-find-instance

        • Core:functional ui-checkout, ui-developer, ui-inventory, ui-service-points, ui-tags, ui-user

        • Update as of Tuesday 3/17: Vega modules marked as released. CF: ui-users pending release, rest released.

        • Updated as of Wednesday 3/18 : ui-users has been released. ui-requests had dependency issues which were addressed by Zak. ui-inventory has dependency issues with stripes-util 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
        UXPROD
        • UIIN-
        1893
      • Jira Legacy
        serverSystem Jira
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-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 LegacyserverSystem JirajqlQueryproject = 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
        • 1021
        • Note: All but mod-event-config (26.x) and mod-sender (26.x) upgraded to RMB 29.x.
      • platform-complete : Missing/unannounced module releases as of Monday 3/16 according to the release spreadsheet (maintainers notified):
        • FSE: edge-patron, edge-sip2, mod-audit, mod-audit-filter, mod-patron, mod-rtac
        • Update as of Tuesday 3/17: All modules marked as released in the spreadsheet or removed from the release.
        • Update as of Wednesday 3/18: mod/edge-patron, mod/edge-rtac and edge-sip2 releases are not compatible with Q1. Matt and Bohdan have been notified. plugin-find-import-profile has dependency issues with stripes-acq-components Taras Tkachenko has been notified.
    • Core Platform development  in Sprint 84
      • RMB 29.3.1 hotfix release to address regressions like  
        Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINVSTOR-455
        . Upgraded mod-inventory-storage 19.1.0 already shipped for Q1.
      • RMB 29.3.2 (branch):
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    jiracounttrue
        • key
    serverSystem JirajqlQueryproject = 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
        • RMB-583
           more complete solution to problems like 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
    2019
        • MODINVSTOR-
    11-12

    Cate Boerema (Deactivated)

    • Second week of second to last development sprint
    • Core functional:Chalmers continues to uncover issues with operational impact such as:
      • Still struggling with 
        • 455
           and a blocker for 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyRMB-575
        • Jira Legacy
          serverSystem
        Jira.  This feature (
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
        MODINVSTOR-357
        • RMB-552
           automatic migrations/module upgrade performance releated
      • RMB 29.4.0 (master):
        • Jira Legacy
          serverSystem
        Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
        UXPROD
        • RMB-
        1626) has taken all quarter and was estimated at 3 days FE/3 days BEFinally got first story
        • 575
           blocker for 
          Jira Legacy
          serverSystem
        Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
        UXPROD
        • MODINVSTOR-
        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://issues.folio.org/secure/Dashboard.jspa?selectPageId=10801)
      • Cap planning team beginning to look at what's there and the capacity for Q1 so we can plan
        • 413
    • Automatic Migrations / Module Upgrade  related:
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyOKAPI-773
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyCIRC-543OKAPI-804
    • Performance related:
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyCHALOKAPI-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 LegacyserverSystem JirajqlQueryproject = uxprod AND type = "new feature" AND (resolution not in
      • 813
         memory leak reported by Martin Tran, heap dumps delivered from the "no dropwizard" branch are invalid, Martin has been asked to repeat tests

    Anton Emelianov (Deactivated)

    • Meeting today to coordinate data prep for bugfest environment 
    • System is up and running now but need POs to go in and do the data setup work but coordinate whether data will be setup before or after Q1 migration
    • Met with 40 plus testers yesterday
    • Only 30% of test cases have been claimed
    • This week will be dedicated to configuring bugfest system and prepping it for Monday
    • About 10 new members have joined bugfest community (many from Germany)

    Goldenrod Focus Tracks

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = 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 2019Q1 2020" ON (20192020-1103-1217) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Jira Legacy
    serverSystem JiraJIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019Q1 2020" ON (20192020-1103-1217) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    20192020-03-11-05

    Jakub Skoczen

  • Started sprint 75
    • Platform Q3.2 updates (dev):Performance-related issues:Ongoing optimisation work in the authn/z subsystem 

    • Platform development  in Sprint 84
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODAT
        RMB-
        51, specifically: 
        583
         a blocker for 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        OKAPI-770
        MODINVSTOR-413
         (blocked in PR due to poor performance) but also for a "keyword" search performance regressions 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        MODINVSTOR-
        2296 to help investigate perf problems going forwardPending perf problems to be addressed by other teams: 
        455
         discovered last week 
    • Automatic Migrations / Module Upgrade  related:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODNOTIFY-54Other perf issues:
        OKAPI-773
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyRMB-
        497 to allow for estimating hitcount and address perf issues like 
        552
         (impact on migration performance)
    • Performance related:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR
        OKAPI-
        256
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-1820
        New development work (RMB 28.x related):
        813
         memory leak reported by Martin Tran, a branch out for testing
    • Q1 2020 Release Management 
      • Most modules upgraded to RMB 29.x on master
      • Modules still without a maintainer/team:
        • mod-login-saml
        • mod-user-import
      • mod-user-import release at risk for Q1 2020 –  Spitfire (responsible for changes in Q1) has no capacity to maintain the module. The Plaform team has picked up 
        Jira Legacy
        serverSystem
        Jira has been completed (in PR) to allow the Functional team to complete 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUIIN-564
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-349
        MODUIMP-9
         to ease the release efforts


    Cate Boerema (Deactivated)

    • Last week of Q1 development
    • Focus in wrapping up Q1 features and must-fix bugs
    • Much of this sprint will be focused on code reviews and creating releases


    Jira Legacy
    serverSystem

    Jira Jira LegacyserverSystem Jira

    JIRA

    serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyRMB-499 to allow addressing 

    jqlQueryproject = 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 "Q1 2020" ON (2020-03-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyUIIN-647Batch import APIs for Inventory:

    Jira Legacy
    serverSystem

    Jira Jira LegacyserverSystem Jira

    JIRA

    serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyMODINVSTOR-353Platform Q3.2 updates (devops):

    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-03-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2227 pending completion on the following tasks
    2020-02-25

    Jakub Skoczen

    counttrue
    • Platform Development in Sprint 83:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        RMB-
        2303 
        559
         – streaming utility for RMB, requested by Kruthi Vuppala (Concorde) for 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        MODINV-
        2298 
        196
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        RMB-
        2268Additionally the following CI problems are being addressed:
        499
         – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        UIIN-
        2315
        647
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-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
        serverSystem Jira
        jqlQuerylabels = q3.2-2019-hotfix
        counttrue
        serverId01505d01-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
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINVSTOR-348
        , 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-1626
         (which had to be implemented differently than the effective location) and 
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-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
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUXPROD-1685
           - Now assigned to Core Platform for Q4
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUIIN-724
           - Which will allow searching by CQL with plans to later implement 
          Jira Legacy
          serverSystem Jira
          columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUXPROD-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
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyCIRC-516
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUICHKOUT-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 LegacyserverSystem JirajqlQueryproject = 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
      • MODINVSTOR-438
      • Okapi bug reports – tested by Hongwei with good results
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-795
           (raised by Hongwei)
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-796
           (raised by Hongwei)
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyOKAPI-509
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc

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

    2019-10-22

    Jakub Skoczen

    • Started sprint 75
    • Platform Q3.2 updates (dev):
      • Security-related:
        keyOKAPI-773
    • Migrations  Discussed Q4 migration performance with Carole Godfrey. Julian has analysed the logs and script and identified long migration time as related to to the "effective location" migration script and not an issue in RMB/Okapi. Specifically for Q4 timeouts should be extended to accommodate long migration time. 
    • Performance Discussed Daisy vs Edelweiss performance with Martin Tran. There has been perf regressions of response time of ~30% for check-in/check-out. It's not clear if it's related to a specific module (e.g Inventory calls saw an improvement). We have speculated that the regression might be related to
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      MODPERMS
      MODAT-
      68 Performance-related issues:
      56
      . Martin will run the test again on a combination of older mod-authtoken and newer Okapi and use Giraffe to try to analyze where the degradation happens. Also, Okapi 2.37 was tested and there's a 30% increase in response times.
    • Search by call number: 
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UICHKIN-111 
        UIIN-985

        Only "lightweight" normalisation for the "eye readable" search will be addressed in Q1. Blocked on 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UICHKOUT
        MODINVSTOR-
        542 CLOSED. The Platform team will continue investigate perf optimisation of the authn/z subsystem through
        444
         which does not require new Platform development (only new index configuration). 
    • Security Audit : three vulnerabilities reported in the first round, four in the second:
      • High: lack of permissions on an endpoint potentially carrying sensitive information – actual severity is lower as the sensitive information is not used for production deployments. Potentially related: 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODAT
        OKAPI-
        51
        767
        , specifically: 
      • Medium: header injection. Fixed in RMB in Q4
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        OKAPI-770
        RMB-478
        lack of rollout in certain module likely cause of the problem
      • Medium: token expiry. Known, 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-
        2296 to help investigate perf problemsPending perf problems to be addressed by other teams: 
        1233
         severity is low due to
        Jira Legacy
        serverSystem
        JiraOther perf issues
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODNOTIFY-54
        MODAT-56
        : 
    • FOLIO DevOps sprint 82:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINVSTOR-256 still shows performance issues after RMB-468 updates, which seems to be related to reporting hit counts
        keyFOLIO-2427
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UXPROD
        FOLIO-
        1820New development work (RMB 28.x related):
        2428
      • Jira Legacy
        serverSystem
        Jira enabler for 
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-349
        FOLIO-2401
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UIIN
        FOLIO-
        564 is going to be addressed this week
      Platform Q3.2 updates (devops)
    • FOLIO DevOps sprint 83:
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-2227
         pending completion on the following tasks:
        FOLIO-2467
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-
        2303 
        2444
    • Release Management  Q1 2020 (Fameflower):

    Cate Boerema (Deactivated)

    • 2 weeks until RMB, Stripes, OKAPI deadline 
    • 3 weeks until general module release deadline
    • Core Functional Q1 2020 features:

    Jira Legacy
    serverSystem

    Jira

    JIRA
    jqlQueryfilter=12064
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2298 

    • In addition to the above features, CF has made significant progress on 
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      FOLIO
      UXPROD-
      2268Additionally the following CI problems are being addressed:
      88
       which wasn't originally targeted for Q1 but the stories were ready and we were blocked on other things (e.g. 
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      FOLIO
      UXPROD-
      2280 related to reference env security, BLOCKED on tasks to upgrade permission handling on individual modules
      2260
       was blocked by 
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      FOLIO-2218 related to scaling issues caused by the increased CI/CD requirementQ3.2 (Daisy) release: Hotfix release issues: (label ^q3.2-2019-hotfix^):
      UXPROD-2246
      )  Lesson: features with ready requirements get developed.  Those that aren't ready are left behind.
    • Core Functional taking Call number searching (thin thread) from Core Platform, as they weren't tracking to get it done

    Jira Legacy
    serverSystem

    Jira
  • 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 LegacyserverSystem Jira

    JIRA
    jqlQuery

    labels = q3.2-2019-hotfix counttrueserverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Cate Boerema (Deactivated)

    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 "Q1 2020" ON (2020-02-25) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-25) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyCHAL-85 and 
    2020-02-18

    Jakub Skoczen

    counttrue
    • Platform Development in Sprint 82:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        CIRC
        RMB-
        516 will need to be hotfixed when complete
        559
         – streaming utility for RMB, requested by Kruthi Vuppala (Concorde) for 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UIIN
        MODINV-
        806
        196
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1
        -ee9b165564fckeyCHAL-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 LegacyserverSystem JirajqlQueryproject = 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
      • -ee9b165564fc
        keyRMB-499
         – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 
        Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUIIN-647
      • Okapi bug reports: 
        • Jira Legacy
          serverSystem
    Jiracounttrue
        • JIRA
    jqlQueryproject = 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

    Jakub Skoczen

    • Mid sprint 74
    • Platform Q3.2 updates (dev):
      • Security-related issues:
        • serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPI-795
           (raised by Hongwei)
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    2019-10-15
        • keyOKAPI-796
           (raised by Hongwei)
    • Discussed Q4 migration performance with Carole Godfrey. Julian has analysed the logs and script and identified long migration time as related to to the "effective location" migration script and not an issue in RMB/Okapi. Specifically for Q4 timeouts should be extended to accommodate long migration time. 
    • Search by normalised call numbers: 
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        OKAPI
        UIIN-
        766
        985
         
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        OKAPI
        UIIN-
        762 Performance-related issues:
        857
         should be considered in requirements analysis phase (not ready for development) latest implementation proposal from Frances Webb addresses most 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UICHKIN
        UIIN-
        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, 
        985
         but not all scenarios (
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1
        -ee9b165564fckeyUICHKOUT-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
        -ee9b165564fc
        keyUIIN-857
        )
    • Security Audit: three vulnerabilities reported so far (details kept private):
      • High: lack of permissions on an endpoint potentially carrying sensitive information – actual severity is lower as the sensitive information is not used for production deployments. Potentially related: 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODAT
        OKAPI-
        51 Pending perf problems to be addressed by other teams: 
        767
      • Medium: header injection. Fixed in RMB in Q4
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODNOTIFY
        RMB-
        54
        478
        Next in-line, Platform team will work to reproduce check-in/check-out perf issues on the perf testing env:lack of rollout in certain module likely cause of the problem
      • Medium: token expiry. Known, 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        CIRC-466
        FOLIO-1233
         severity is low due to
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UXPROD
        MODAT-
        1820New development work (RMB 27.x related) has been resumed this week
        56
        : 
    • FOLIO DevOps:
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-256 pending verification (on hold due to dev vacation)
        FOLIO-2427
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR
        FOLIO-
        349
        2428
         enabler for 
      • Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UIIN
        FOLIO-
        564 is nearing completion
      Platform Q3.2 updates (devops):
    • Release Management Q1 2020 (Fameflower):

    Jira Legacy
    serverSystem

    Jira  Jira LegacyserverSystem Jira

    JIRA

    serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyFOLIO-2303

    jqlQueryproject = 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 "Q1 2020" ON (2020-02-18) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2298 

    Jira Legacy
    serverSystem

    Jira Jira LegacyserverSystem Jira

    JIRA

    serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyFOLIO-2268Additionally the following CI problems are being addressed:

    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-18) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyFOLIO-2280 related to reference env security
    2020-02-11

    Cate Boerema (Deactivated)

    • Discussion of how to store
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      FOLIO-2218 related to scaling issues caused by the increased CI/CD requirement
      UXPROD-81
       data is ongoing
      • Vince and Marc were able to agree that the first step is to store check-ins so we will do that now which will allow us to complete the feature (because the data will be persisted)
      • More conversations are still needed to decide on whether and how to use mod-audit for storing and reporting on this data.  See comments in this story for some of the considerations: 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO
        CIRCSTORE-
        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^)
        182
    • Per the Thunderjet team, it's best to wait before using PubSub until some performance issues have been addressedTesting hotfixes for Chalmers issues:
      • Given this, Core Functional will hold off on pursuing PubSub to address data synchronization:
        • Jira Legacy
          serverSystem
        Jira
        • JIRA
        jqlQuerylabels = q3.2-2019-hotfix counttrue
        • serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUIREQ-378
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Cate Boerema (Deactivated)

        • keyUIREQ-345
    • Core Functional is picking up
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      CHAL
      MODINVSTOR-
      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.
      439
      from Concorde but is blocked awaiting Core Platform work
    • Core Functional is considering picking up 
      Jira Legacy
      serverSystem
      Jira
      JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      key
      CHAL
      UXPROD-
      54 - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
      2185
       from Core Platform, as this work is delayed.  Might be a good way to expose some additional backenders to RMB.
    • Need to analyze state of Q2 requirements

    Jakub Skoczen

    counttrue
    • sprint 82
    • Platform Dev section: 
        • in the current sprint two tickets are being investigated:
          • Jira Legacy
            serverSystem
        Jira
          • JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            key
        CHAL
          • OKAPI-
        52 - Waiting for hotfix releases to be prepared and applied to BugFest 3.1 and 3.2
          • 795
             (raised by Hongwei)
          • Jira Legacy
            serverSystem
      Jira
          • JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            key
      CHAL
          • OKAPI-
      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
          • 796
             (raised by Hongwei)
      • Limited capacity to address functionality related tickets – issues will be evaluated and priotized on a case-by-case basis, so far the following items are planned for Q1:
        • Jira Legacy
          serverSystem
      Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
      CHAL
        • RMB-
      43
        • 500
       Waiting
        •  – support for
      "refined design" from FilipWriting additional stories
        • streaming "downloads" (note: bulk "imports" were added to Inventory instances/holdings/items by the team in Q4 and had good feedback from migrations), requested by Kruthi Vuppala (Concorde) for 
          Jira Legacy
          serverSystem
      Jira
        • JIRA
          serverId01505d01-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
        • MODINV-196
        • Jira Legacy
          serverSystem
      Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
      UXPROD
        • RMB-
      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 LegacyserverSystem JirajqlQueryproject = 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
        • 499
           – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUIIN-647
        • Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODINVSTOR-435
           and 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyCIRCSTORE-184
           – requested by BNCF for slow open loan queries, 

          https://folio-project.slack.com/archives/C9BBWRCNB/p1579860339261200

        • pending Q1 requests: 
          Jira Legacy
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    jiracounttrue
        • key
    serverSystem JirajqlQueryproject = 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
        • UXPROD-2185
           (search by normalised call number)
    • In addition, the following remaining DevOps tasks have/are being completed this sprint:
      • 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
          serverSystem JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
    2019-10-08
      • FOLIO-2386
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-2426
      • Jira Legacy
        serverSystem
        Jira back in OPEN for another review. Additional, tasks ongoing
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UICHKIN-111
        FOLIO-2427
      • Jira Legacy
        serverSystem
        Jira 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
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODAT-51
        FOLIO-2428
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-2401
      • Jira Legacy
        serverSystem
        JiraThe ticket to replicate check-in/check-out performance issues on the Perf test env by adding more realistic circulation data is pending:  Jira LegacyserverSystem Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODNOTIFY-54
        FOLIO-2336

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = 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 "Q1 2020" ON (2020-02-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyCIRC-466

    Jira Legacy
    serverSystem

    Jira Jira LegacyserverSystem Jira

    JIRA

    serverId01505d01-b853-3c2e-90f1-ee9b165564fckeyUXPROD-1820New development work (RMB 27.x related) has been resumed this week:

    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-11) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyMODINVSTOR-256 pending verification
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINVSTOR-349
     enabler for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-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
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyFOLIO-2227
     which consists of the following sub-tasks: Jira LegacyserverSystem Jira
    2020-02-04

    Cate Boerema (Deactivated) - Repeating my update from last week because we didn't get to discuss it.

    • Q1 planning finalized.  See dashboard.

    • Q4 release closed.  
      • Statistics: Cross Release Statistics
        • In the end, the amount of work completed in Q4 2019 was very comparable to Q3 2019
        • That said, we clearly over-committed compared with previous quarters.  We committed to almost twice what we completed, resulting in a high percentage of "spillover" features.  Potential reasons:
          • Failure to account for increased bug fixing given we now have a production user
          • UNAM team dropping out
          • Over-commitment by teams not using the cap plan for planning (e.g. @Cult, Course reserves)
          • Requirements not ready for Export 
          • Technical dependencies between teams
        • For Q1, we have taken measures to avoid this issue:
          • Accounting for more bug fixing in the cap plan
          • Being more careful about accounting for technical dependencies and requirements readiness in planning
          • Our baseline committed feature count (90 features) is much more in line with previous quarters.
    • Other news:
      • Darcy Branchini taking over for Khalilah as lead PO for Vega
      • Core Functional putting 
        Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO-2275
        UXPROD-501
         on hold, as it is blocked by fee/fine work (
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO-2265
        UXPROD-2246
        )
      • To replace this work, Core Functional has begun development on 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        FOLIO-2267
        UXPROD-88
         which had previously been scheduled for Q2 
      • Discussing storage of 
        Jira Legacy
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e
        -90f1-ee9b165564fckeyFOLIO-2268Additionally the following CI problems are being addressed:
        -90f1-ee9b165564fc
        keyUXPROD-81
         data
        • In house use is looking like just a type of circulation data which ought to be captured in the circulation log (planned to leverage mod-audit)
        • While circ log was not deemed MVP, In house use was
        • This means we need to consider getting mod-audit fit for purpose.  See comment here, for Vince's thoughts on steps: 
          Jira Legacy
          serverSystem
          Jira
          JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
          FOLIO
          CIRCSTORE-
          2060
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyFOLIO-2276
        • 182
      • Anne-Marie is scheduling a knowledge sharing meeting on PubSub with from Core Functional, Thunderjet and Folijet to discuss what impact this may have in your apps.  Core Functional has a couple of bugs it has on hold awaiting a stable version of PubSub:
      • 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
          serverSystem
          Jira
          JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
          FOLIO
          UIREQ-
          2282
          378
        • Jira Legacy
          serverSystem
          Jira
          JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
          FOLIO-2237
      Q3.2 (Daisy) release:
        • UIREQ-345

    Jira Legacy
    serverSystem

    Jira

    JIRA
    jqlQuery

    labels = q3.2-2019-hotfix

    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 "Q1 2020" ON (2020-02-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-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 LegacyserverSystem Jira

    -3c2e-90f1-ee9b165564fc

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-02-04) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    keyCHAL-49
  • Filip is helping us to design a solution for 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyCHAL-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 LegacyserverSystem JirajqlQueryproject = 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 counttrue
    2020-01-29

    Jakub Skoczen

    serverSystem JirajqlQueryproject = 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 counttrue
    • combined sprint – 80 and 81
    • Starting from sprint 80 the Platform team is being restructured:
    • Platform Dev section: 
      • with the departure of EBSCO developers (Eric and Hongwei) Dev sub-team has been reduced to 2 devs: Adam (IndexData) and Julian (OLE/GBV)
      • Dev team will remain responsible for maintenance of Platform components – Okapi, RMB and authentication/authorization (mod-permissions/mod-authtoken/mod-login).
      • Performance optimisations remain a strong focus area:
        •  in Q4 2019 various inventory search/filtering and authentication/authorization perf improvements were delivered, many of which has had positive impact across the entire platform, including high-level circulation operations like check-in and check-out
        • in Q1 2020 the team will focus on generic solutions to improve business-logic layer (check-in/check-out/renewals but also other API operations, best combined with local optimisations in individual modules but capacity in the functional teams remains a challenge) and core infrastructure performance (Okapi/mod-authtoken/mod-permissions) plus any specific perf issues raised by the community.
        • in the current sprint two tickets are being investigated:
          • Jira Legacy
            serverSystem JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    Jira Legacy
          • keyOKAPI-795
             (raised by Hongwei)
          • Jira Legacy
            serverSystem JIRA
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            key
    2019
          • OKAPI-
    10-01
    • Mid Sprint 73
    • Platform Q3.2 updates (dev):
      • Various security-related issues brought up last week took precedence over other work:
        •  
          • 796
             (raised by Hongwei)
      • Limited capacity to address functionality related tickets – issues will be evaluated and priotized on a case-by-case basis, so far the following items are planned for Q1:
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPIRMB-763
           solution
          500
           – support for streaming "downloads" (note: bulk "imports" were added to Inventory instances/holdings/items by the team in Q4 and had good feedback from migrations), requested by Kruthi Vuppala (Concorde) for 
          Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyFOLIOMODINV-2287196
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyOKAPIRMB-764
           solution
          499
           – support for normalised searching of ISBN (and ISBN-like) fields, requested by Cate and Charlotte for 
          Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyFOLIOUIIN-2286647
        • Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyRMB-478
        Chalmers-related performance and stability issues:
        • MODINVSTOR-435
           and 
          Jira Legacy
          serverSystem JiraJIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyUICHKINCIRCSTORE-111
           all individual backend tickets have been addressed (for list see previous report) besides:
          184
           – requested by BNCF for slow open loan queries, 

          https://folio-project.slack.com/archives/C9BBWRCNB/p1579860339261200

        • pending Q1 requests: 
          Jira Legacy
          serverSystem
          Jira
          JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
          MODAT
          UXPROD-
          51
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODPERMS-67
        • Jira Legacy
          serverSystem Jira
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyMODUSERS-150
        • Problems to be addressed by other teams are still incomplete:
          • Jira Legacy
            serverSystem Jira
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            keyMODSOURCE-76
             
          • Jira Legacy
            serverSystem Jira
            serverId01505d01-b853-3c2e-90f1-ee9b165564fc
            keyMODNOTIFY-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 LegacyserverSystem Jira
          2185
           (search by normalised call number)
      • Limited capacity to keep maintaining orphaned and "no clear maintainer" modules, this includes:
        • mod-users
        • mod-users-bl
        • mod-user-import
        • mod-login-saml
        • mod-configuration
    • Platform DevOps resources (Ian, John and David) are being consolidated with the IndexData DevOps team. Until the project finds replacements or additional resources, ID DevOps will provide ongoing, steady-state support for:
      • maintenance of reference environments: folio-snapshot, folio-snapsthot-stable, folio-testing,
      • maintenance of the CI and build infrastructure (Jenkins) — integration, builds and testing for FOLIO modules
      • maintenance of the FOLIO Kubernetes cluster and related environments (e.g continuous snapshot environment, migrations env, performance env)
      • help with design and tooling for production-ready FOLIO deployments (systems documentation and diagrams, examples)
      • supporting FOLIO Release Management -- Q1 2020
      • general infrastructure support for FOLIO developers
    • In addition, the following remaining DevOps tasks have/are being completed this sprint:
      • Jira Legacy
        serverSystem JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        CIRC
        FOLIO-
        466
        2386
      • Jira Legacy
        serverSystem
        JiraNew development work (RMB 27.x related) has been resumed this week:
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UXPROD-1820
        FOLIO-2426
      • Jira Legacy
        serverSystem
        Jira pending verification
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-256
        FOLIO-2427
      • Jira Legacy
        serverSystem
        Jira enabler for 
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        MODINVSTOR-349
        FOLIO-2428
      • 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
        serverSystem
        Jira
        JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
        UIIN-564 is back in development
      Platform Q3.2 updates (devops):
      • FOLIO-2401
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-2227
         which consists of the following sub-tasks:
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyFOLIO-2275
        • Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyFOLIO-2265
        keyFOLIO-2336


    Cate Boerema (Deactivated)

    • Q1 planning finalized.  See dashboard.

    • Q4 release closed.  
      • Statistics: Cross Release Statistics
        • In the end, the amount of work completed in Q4 2019 was very comparable to Q3 2019
        • That said, we clearly over-committed compared with previous quarters.  We committed to almost twice what we completed, resulting in a high percentage of "spillover" features.  Potential reasons:
          • Failure to account for increased bug fixing given we now have a production user
          • UNAM team dropping out
          • Over-commitment by teams not using the cap plan for planning (e.g. @Cult, Course reserves)
          • Requirements not ready for Export 
          • Technical dependencies between teams
        • For Q1, we have taken measures to avoid this issue:
          • Accounting for more bug fixing in the cap plan
          • Being more careful about accounting for technical dependencies and requirements readiness in planning
          • Our baseline committed feature count (90 features) is much more in line with previous quarters.
    • Other news:
      • Darcy Branchini taking over for Khalilah as lead PO for Vega
      • Core Functional putting 
        Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
    FOLIO-2267
      • UXPROD-501
         on hold, as it is blocked by fee/fine work (
        Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
    FOLIO
      • UXPROD-
    2268Additionally the following CI problems are being addressed:
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyFOLIO-2060
      • 2246
        )
      • To replace this work, Core Functional has begun development on 
        Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
    FOLIO-2276
      • UXPROD-88
         which had previously been scheduled for Q2 
      • Discussing storage of 
        Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        key
    FOLIO
      • UXPROD-
    2282
      • 81
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyFOLIO-2237
    • Q3.2 (Daisy) release:release pending on a bugfix for 
      •  data
        • In house use is looking like just a type of circulation data which ought to be captured in the circulation log (planned to leverage mod-audit)
        • While circ log was not deemed MVP, In house use was
        • This means we need to consider getting mod-audit fit for purpose.  See comment here, for Vince's thoughts on steps: 
          Jira Legacy
          serverSystem
    Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
    UIU
        • CIRCSTORE-
    1271 which should be available related todayduring 
        • 182
      • Anne-Marie is scheduling a knowledge sharing meeting on PubSub with from Core Functional, Thunderjet and Folijet to discuss what impact this may have in your apps.  Core Functional has a couple of bugs it has on hold awaiting a stable version of PubSub:
        • Jira Legacy
          serverSystem
    Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          key
    UIU
        • UIREQ-
    1271 another problem has been discovered, 
        • 378
        • Jira Legacy
          serverSystem
    Jira
        • JIRA
          serverId01505d01-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: 
        • UIREQ-345

    Jira Legacy
    serverSystem JIRA
    jqlQueryproject = 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 "Q1 2020" ON (2020-01-29) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Jira Legacy
    serverSystem

    JirajqlQueryfilter=11808

    JIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q1 2020" ON (2020-01-29) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

  • Have created first pass at release notes accessible from here: Release Notes
    • Q3 needs to be wrapped up in JIRA.  There are still ~10 open UXPRODs
    2020-01-21

    Weekly status cancelled due to WOLFcon

    Jira Legacy
    serverSystem JiraJIRA
    jqlQueryproject = 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 2019Q1 2020" ON (20192020-1001-0121) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc

    Jira Legacy
    serverSystem JiraJIRA
    jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q4 2019Q1 2020" ON (20192020-1001-0121) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
    counttrue
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc





    ...