Versions Compared

Key

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

...

Report Date

Overall Status Update

Q1 Feature Count on Report Date



FunctionalNFR
2019-09-10

Jakub Skoczen

  • Sprint 71
  • Platform Q3.2 updates (dev):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1820
       RMB 27, more releases last sprint, new features completed and more in progress
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-385
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-457
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-468
         potential solution for the following perf issues:
    • Chalmers-related issues:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyCIRC-447
         solution for 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUIREQ-335
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyOKAPI-759
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyOKAPI-760
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODUSERS-147
         brought up today by Cate, to be discussed at Platform's standup
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUICHKIN-111
         perf-related, no longer assigned to anyone since beginning of the week, discussed with Cate today and it will be brought up at the Platform stand-up (backend portion of the problem may be addressed)
  • Platform Q3.2 updates (devops):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1827

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2011
         has been completed, test PR available at https://github.com/folio-org/platform-core/pull/382
      • Remaining FOLIO-1827 blockers: 
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2056
        , which is blocked on:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2249
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2227
  • Q3.2 (Daisy) release:

Cate Boerema

  • Module release deadline for Q3.2 (Daisy) is end of day today
  • Many PRs for circulation (mod-circulation) came in about a week before the deadline and Marc Johnson asked for priorities, as it didn't seem they would all be able to be reviewed in time.  POs prioritized features affecting Chalmers.

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-09-10) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-09-10) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-08-27

Jakub Skoczen

  • Sprint 71
  • Platform Q3.2 updates (dev):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1820
       RMB 27 initial release performed last week, includes clean-up and bugfixes for RMB26 series, new functionality:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-459
         
        which (once RMB27 is rolled out to storage modules, see
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODUSERS-142
         and
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODINVSTOR-342
        ) will address 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2102
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-452
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-451
      • Many other fixes, full list here: 
        Jira
        serverFOLIO Issue Tracker
        jqlQueryproject = RMB AND fixVersion = 27.0.0
        counttrue
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49

      • tickets that are in the pipeline for the next RMB27.x releases:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-454

          RMB26 regression, not critical for existing functionality 
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-385
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-457

          helper utility to address remaining performance problems: 
          Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyMODINVSTOR-256
           and 
          Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyMODINVSTOR-336
  • Platform Q3.2 updates (devops):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1827

      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2011

        is finally in the sprint, the plan is to rollout PR preview functionality to "platform-core" this sprint. It will work on top of the new FOLIO K8s-based CI cluster but initially will include several limitations, e.g no ability to user "feature branch builds". This ability will be developed in the coming weeks and the architecture for it has been agreed last week (see 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2227
        )
      • Remaining FOLIO-2011 blockers: 
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2194
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2056
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2217
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1815
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2169
  • Scaling FOLIO development process:
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyFOLIO-2214
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyFOLIO-2207
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyFOLIO-2208
  • Q3/Q4 platform features in DRAFT (requirements and design):
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1928
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1826

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-08-27) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-08-27) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-08-13

Jakub Skoczen

  • Sprint 70
  • Platform Q3.2 updates:
    • General platform bugfixes for Q3.2:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2102
         
        Spike: timestamp metadata missing from bootstrap data (spillover)
    • UXPROD-1818  CLOSEDRMB 26 release features and core module rollout (performance, array search and cross-table search)
      • released RMB 26.4.0, includes performance fixes for slow item.barcode search (
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODINVSTOR-292
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-411
         
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-432
      • completed large new functionality 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-395
         which will help address remaining performance issues (filtering by location and status)
    • UXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2187
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2194
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2056
  • Platform Q3.2 work:
  • Q3.1 Release Management:
  • Scaling FOLIO development process:


Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-08-13) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-08-13) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-08-06

Jakub Skoczen

  • Mid sprint 69
  • Platform Q3.1 updates:
    • General platform bugfixes for Q3.1:
      • RMB-432 - fulltext: word splitting and punctuation removal IN PROGRESS  and  
      • RMB-438 - contributor search returns no results when name contains "-" IN PROGRESS , which block many UI issues, serious but not critical for Q3.1, related to searching terms that include punctuation like apostrophes and hyphens. 
      • FOLIO-2102 - Spike: timestamp metadata missing from bootstrap data OPEN
    • UXPROD-1818 - RMB 26 release features and core module rollout (performance, array search and cross-table search) IN PROGRESS
      • released RMB 26.2.4 (MODINVSTOR-319) and rolled it out to mod-inv-storage (to be released today), RMB 26.2.3 (CIRCSTORE-138) rolled out to mod-circulation-storage (released) and RMB 26.2.2 rolled out to mod-users (released) 
      • Continued focus on performance testing and tuning:
        • Overall perf results look very good (here)
        • RMB-395 - support nested sub queries across multiple tables IN PROGRESS  is developed to address two remaining perf test issues:  
          • MODINVSTOR-256 - /instance-storage/instances?query=holdingsRecords.permanentLocationId=abc* does not perform BLOCKED
          • MODINVSTOR-292 - Search instances by item.barcode is slow BLOCKED  
    • UXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
      • FOLIO-2183 - integrate backend-module pipeline into Jenkins CLOSED
      • FOLIO-2187 - refactor Ansible roles so they can be used on K8s IN PROGRESS
      • FOLIO-2194 - Develop script to clean up expired K8 container instances OPEN
      • FOLIO-2056 - create a pipeline for a front-end module that builds and deploys to K8s cluster OPEN
      • FOLIO-2195 - Implement EFK logging stack on folio-eks-oregon-1 K8 cluster CLOSED
      • FOLIO-2131 - SPIKE: how to deploy containers based on feature branches IN PROGRESS
  • Platform Q3.2 work:
  • Q3.2 Release Management:
    • the integration tests have been updated to pass on the Q3.1 release and a release tag q3.1-2019 has been created

      • FOLIO-2192 - Integrate Q3.1 module releases into platform-core and platform-complete CLOSED
    • mod-login-saml bugfix release 1.2.2 has been released by the Platform team, this module needs maintainers for Q3.2 and Q4.
    • Q3.1 module bugfix release deadline is August 8th, midnight GMT 
    • The “Modules and version” release planning spreadsheet for Q3.1: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0 
  • Scaling FOLIO development process:
    • "FOLIO Tech Design and Code Review process and roles" document: https://docs.google.com/document/d/10cTOkUBpi7myIBQfrvdLGihLE1Wes3rRxFgDZs-Is64/edit#
    • Finalized PR review guidelines and initial CODEOWNERS groups are ready. Next steps planned for sprint 70:
      • publish the PR review checklists on dev.folio.org and create a template for PRs that links to it
      • publish CODEOWNERS files in mod-inventory/-storage, mod-circulation/-storage
      • propose a process for bringing up technical designs for comments on the #tech-leads channel

Cate Boerema

  • Only one must-fix q3.1 bug remains open and it's in review
  • Most bugs discovered during bugfest were not deemed must-fix for 3.1
  • Otherwise teams are just plugging along with Q3 development

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-08-06) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-30) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49


2019-07-30

Cate Boerema

  • Module release deadline for the Q3.1 release was last Wednesday
    • It was close, but we managed to close all bugs and must-fix stories in time (see dashboard).  There is one open bug for UNAM - I will follow up with Holly on that.
    • There is some spillover on 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1653
      which has proved a very complex feature to develop
      • Must fix for Q3.2: 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyCIRCSTORE-142
          (I would caution Chalmers against using this feature until these bugs have been addressed)
      • Nice to have: 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUIREQ-294
         
    • General UI performance issues (
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keySTCON-85
      ) were significantly improved but not completely alleviated. Per Michal, "there is nothing else we can do about this. I feel like we did everything possible given our current architecture (stripes-connect, redux-form). In order to improve it we would have to restructure things significantly (replace redux-form and switch to GraphQL)."  Status on that initiative?
  • Cap planning and MVP
    • Cap plan will be updated this evening and so POs are being asked to do any last rankings (there are still some who haven't done the assignment - see unranked features)
    • Cap planning team needs to assemble proposal for PC by Aug 8th
    • Discussion tomorrow with cap plan group, Charlotte and select MM SMEs on how we can best evaluate what Inventory features are must have for MVP
    • Jump in functional features targeted for Q3 (see stats on right - we are now targeting 140 functional issues up from 134 two weeks ago) is, in part, due to POs breaking down their features so they can be better ranked.  After evaluation, some may be removed from Q3

Jakub Skoczen

  • Started sprint 69
  • Platform Q3.1 updates:
    • General platform bugfixes for Q3.1:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODINVSTOR-319
         regression when new style array search is mixed with a filter that requires a DB view (e.g location search), resolved. Issues like this will be addressed wholesale when RMB-395 is completed.
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-432
         and 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-438
        , which block many UI issues, serious but not critical for Q3.1, related to searching terms that include punctuation like apostrophes and hyphens. While RMB-438 would address also 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUIREQ-295
         /
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyCIRCSTORE-138
        we decided to expedite a fix for this issue through 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyRMB-439
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2102
    • UXPROD-1818 - RMB 26 release features and core module rollout (performance, array search and cross-table search) IN PROGRESS
      • released RMB 26.2.4 (MODINVSTOR-319) and rolled it out to mod-inv-storage (to be released today), RMB 26.2.3 (CIRCSTORE-138) rolled out to mod-circulation-storage (released) and RMB 26.2.2 rolled out to mod-users (released) 
      • Continued focus on performance testing and tuning:
        • Overall perf results look very good (here) and the new early warning system for missing indexes is extremely useful for catching potential perf issues before they manifest on a system with large data sets, all warnings seen for Q3.1 have been addressed through 
          Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2176
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-395
           is developed to address two remaining perf test issues: 
          Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyMODINVSTOR-256
           and 
          Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyMODINVSTOR-292
           
    • UXPROD-1827 - CI-integrated continuous deployment (Q3, FOLIO setup) IN PROGRESS 
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2183
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2187
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2194
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2056
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2195
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2131
  • Platform Q3.2 work:
    • UXPROD-1815 - support for upgrading schemas without complete reload of data (DB migrations)IN PROGRESS
      • FOLIO-2169 - SPIKE investigate schema migrations in platform-core storage modules IN PROGRESS roughly specced out the requirements and scope, Taras has begun work on the SPIKE in Sprint 68
  • Q3.2 Release Management:
  • Scaling FOLIO development process:

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-07-30) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-30) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-07-16

Jakub Skoczen

  • Started sprint 68
  • Platform Q3.1 updates:
    • General platform bugfixes critical for Q3.1:
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyMODAT-47
         which addresses the problem reported in 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyCIRC-379
         a Pull Request is ready but requires refactoring
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1818

      • Most UI bugs resolved (confirmed) or reassigned to front-end developers (Core: functional), one remaining:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-432
      • Continued focus on performance testing and tuning:
        FOLIO-2143 uncovered some performance issues which have been addressed in Sprint 67
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-429
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-417
      • and some bugs that are being addressed this sprint:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-430
      • Overall perf results look very good and the new WARNING system for missing indexes is extremely useful for providing new performance optimizations
      • New feature development for:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyRMB-395
           likely shipped in RMB 27 to address the remaining perf issues (item.barcode and holdings.location search)
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1827

      • AWS/EKS cluster set up tasks completed (including ingress and Ansible roles)
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2055
         to be completed this week
      • Added several SPIKEs this sprint for remaining issues:
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2131
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2130
        • Jira
          serverFOLIO Issue Tracker
          serverId6ccf3fe4-3301-368a-983e-20c466b11a49
          keyFOLIO-2089
  • Platform Q3.2 work already begun:
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1815
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyFOLIO-2169
         roughly specced out the requirements and scope, Taras has begun work on the SPIKE in Sprint 68
  • Q3.2 Release Management:
    • The “Modules and version” release planning spreadsheet for Q3.1 is ready: https://docs.google.com/spreadsheets/d/14zoV755B1kh5_j2CTzYAmHo1_N46RGh5-B4lyG6Qht8/edit#gid=0
    • As usual, lead maintainers will update the “Release Version” and “Interface Required/Provided” columns. If there is a bugfix release for Q3.1 (released past the module release deadline) they will also update the “Bugfix release version” column.
    • Q3.1 module release deadline is July 24th, midnight GMT 
    •  Q3.1 module bugfix release deadline is August 8th, midnight GMT 
  • Scaling FOLIO development process:

Cate Boerema

  • Q3.1 must-fix bugs and features are moving along.  Key updates:
    • Bugs:
      • Critical performance bug is making large parts of FOLIO nearly unusable (Users, Inventory etc): 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keySTCON-85
          Michal has a fix in code review, but it's complex and his first PR had to be reworked
      • Stripes issue causing many search bugs in Inventory is In review: 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keySTSMACOM-229
          This fix should significantly improve searching experience in Inventory
      • I just noticed this bug on the dashboard (it wasn't assigned a development team).  We need to get this assigned to a team with backend capacity: 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyCIRC-390
    • Features:
      • Moving requests from one item to another - All major stories have been completed but a couple have been re-opened due to failed scenarios.  Still tracking for completion by next Wed (module release deadline)
      • Title level and item level requests - Magda and team working through last issues now that they have integration environment working
      • SIP2 - Magda and team working on PIN verification
  • Beyond Q3.1 for Core Functional
    • Inventory notes feature completed
    • Lots of new controlled vocabularies added for instance record
    • Charlotte readying additional stories for development
    • Also prioritizing wrapping up wiring in of loan policy settings around hold requests 
  • Permissions
    • Have been testing user app permissions and there are issues (lots of permissions give access to more than they should while others are missing things which result in errors when working)
      • Have updated the Users app permission tab and discussed with Emma, Holly and Patty
      • Need to create a user story for cleanup
      • In the meantime, it's really important that we find out what permission sets Chalmers intends to use and make sure they work (Anton is looking into this)

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-07-16) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-16) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-07-09

Jakub Skoczen

Cate Boerema

  • All Core Functional must-haves for 3.1 are In review or In progress: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10628
  • Moving requests from one item to another is tracking for completion
  • Also making progress on Inventory cleanup (adding controlled vocabularies, notes etc.)
  • Fixing some critical Inventory search bugs with lots of help from Core Platform
  • Added release notes and stats from Q2: Release Notes
  • Capacity planning team working through process for MVP proposal
    • Have discussed assignment for POs (will share with them at PO meeting tomorrow)
    • Harry has put together a good deck on goals and process
  • SIGs continue to do re-ranking - lots of good discussions and many things are being considered lower priority than previously ranked.  Ranks are not always being updated in JIRA perhaps due to organizational process delays?

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-07-09) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-09) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

2019-07-02

Cate Boerema

  • Q2 Clover release live as of yesterday!
  • Release notes and statistics will be available by end of week
  • Next big release is Q3 Daisy
    • Dashboard: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10627
    • Team plans are still being worked out, but each team has enough to get started
    • Q3 plans may evolve over the course of the quarter as we get the results of the SIG re-ranking exercise and with the capacity planning group's proposed plan for summer 2020
  • Next interim release is Q3.1
    • This is the release Chalmers will go live on
    • Module release deadline is July 24th, release is August 12
    • Anton has created a dashboard for bugs and we have extended to include the must-have features for the release, as well.  May also include the must-have stories.  
  • Capacity planning group meeting every couple of days with goal to have a plan for how the release proposal will be made prior to the stakeholder meeting
  • SIGs are working with POs to re-rank features.  Meetings I have attended so far have been really productive.
  • Core functional team:
    • Focus on the must-have bugs and features for Q3.1:
      • SIP2
      • Title level requests
      • Move requests from one item to another
    • Also working on Inventory cleanup:
      • Search bugs and enhancements - Charlotte is coordinating joint SME/Dev discussions on search to help identify the highest impact fixes.
      • Completing incomplete features in instance, holding and item
      • Niels Erik will be available on Core team full-time in July (apart from planned vacation)

Jakub Skoczen

Jira
serverFOLIO Issue Tracker
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 "Q3 2019" ON (2019-07-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Jira
serverFOLIO Issue Tracker
jqlQueryproject = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels = NFR AND fixVersion was "Q3 2019" ON (2019-07-02) ORDER BY cf[10002] ASC, assignee ASC, summary ASC
counttrue
serverId6ccf3fe4-3301-368a-983e-20c466b11a49





...