Releases
Page tree
Skip to end of metadata
Go to start of metadata

Important Upgrade Considerations

This section outlines all changes that require special consideration for customers in production.  Configuration changes may be needed to prevent operational interruptions.  See checklist for guidelines on how to fill this out. 

Changes and Required Actions


Functional AreaChange or AdditionConsiderationsAction requiredAction timingContact personCommentsRelated JIRA issues
Affected app or moduleWhat has been changed or added that should be noted for this releaseWhat challenges may arise related to this change or additionIf applicable, detail what action(s) must be taken hereWhen can the action be taken (before, during or after upgrade)User name of person that can provide additional detailName of user leaving comment: comment on what you encountered or ask a question @mention Contact personInclude issue link for bug fix, story or feature that applies

Platform

There are be significant breaking changes to mod-login in this release.  The API has changed as follows:

  • POST /authn/credentials - will now return 201 with no body upon successful credential creation. 
  • GET /authn/credentials - Removed. 
  • GET /authn/credentials/<id> - Removed.  
  • PUT /authn/credentials/<id> - Removed. 
  • DELETE /authn/credentials/<id> - Replaced by: DELETE /authn/credentials?userId=<userId>. 

It will no longer be possible to manually get or update credential hashes/salts.

Administrative/Operational scripts may need to be adjusted if these API endpoints are used.

Update any scripts as neededAfter upgrade

Craig McNally

While these types of breaking changes may be disruptive, the FOLIO Security Team decided it was worth it since these changes addressed fairly significant security vulnerabilities and the scope of required changes within FOLIO was limited.

MODLOGIN-128 - Getting issue details... STATUS

MODLOGIN-133 - Getting issue details... STATUS

MODLOGIN-134 - Getting issue details... STATUS

PlatformRMB requires all PostgreSQL extensions to be loaded into public schema (RMB-584)

Upgrading may fail with this PostgreSQL error (MODORDSTOR-161): "public.gin_trgm_ops" does not exist

Manually run this SQL in the modules database (okapi_modules for folio-ansible, folio for single-server) (RMB-675):
ALTER EXTENSION pg_trgm SET SCHEMA public		Immediately before starting the upgrade

Julian Ladisch


RMB-675 - Getting issue details... STATUS

mod-kb-ebsco-javaStoring Knowledge Base configuration has been moved from mod-configuration to mod-kb-ebsco-javaUnless we migrate those credentials to the correct location, eHoldings app might not work as expected. Please note that this script needs to be run for upgrades that involve data migration. For fresh installs of goldenrod, users can update configuration in Settings - eHoldings - knowledge base from UI.Run the script attached by filling in okapi endpoint and token kb-migration.shAfter upgrade

Sobha Duvvuri Carole Godfrey

Dmytro Tkachenko

This has to be the practice until cross-module data migration is supported in FOLIO

RAML Module Builder

RAML Module Builder 30.x includes changes to some of the functions used in database index definition.

This means that an upgrade to a module version using RAML Module Builder 30.x will likely recreate some of the existing database indexes.

As version 30.x is the officially supported version of RAML Module Builder for Goldenrod, it is likely that most storage modules are affected by this.

The process of recreating database indexes   can take a considerable amount of time (in some cases, multiple hours).Plan downtime appropriately. Potentially change timeouts or similar for clients or intermediaries of the upgrade process.Prior to upgrade

Jakub Skoczen

Julian Ladisch


RMB-583 - Getting issue details... STATUS

RMB-587 - Getting issue details... STATUS

Platform

There are changes in the steps/order of operations when upgrading an existing instance of Folio and its respective tenant(s).

Breaking change with the introduction of Okapi SYS# permissions.

RMB requires all PostgreSQL extensions to be loaded into public schema (RMB-584).

There can no longer be a single post of an install.json file to Okapi's tenant install endpoint for an upgrade.

Administrative/Operational procedures and scripts may need to be adjusted.

Upgrading may fail with this PostgreSQL error: "public.gin_trgm_ops" does not exist

If your upgrade fails and you roll back your instance and database, you will need to restart the mod-agreements, mod-licenses and mod-permissions modules before attempting another upgrade.

These components must be upgraded for the tenant in the  order below, ahead of posting the full install.json to Okapi's tenant install endpoint:

-Okapi module 3.1.2

-mod-pubsub

-mod-permissions

-mod-authtoken


Those storage modules which introduce RMB-675 database changes must be enabled for the tenant ahead of the others. mod-orders-storage was updated for Q2 platform-complete, and mod-calendar was updated for Q2 platform-core. You can also manually run this SQL in the okapi_modules database:

ALTER EXTENSION pg_trgm SET SCHEMA public;

Prior to upgrade

Jason Root Wayne Schneider Hongwei Ji Sobha Duvvuri

This process is still very brittle, and your results will vary depending on:

-If you are coming from the "latest" released Q1 versions of modules, the initial released Q1 versions of modules, or some other mash-up of module versions released prior to Q2.

-If your Okapi is secured or not.

-If you are incremental upgrading, or upgrading all at once.



FOLIO-2662 - Getting issue details... STATUS

custom-fields (mod-users)Custom TEXT fields have newly added attribute fieldFormat in Goldenrod
"textField" : {
      "fieldFormat" : "TEXT"
}
Custom TEXT fields created in Fameflower and migrated to Goldenrod will need added fieldFormat attribute. 
Without attribute, Exception is observed adding custom fields or assigning custom field to user.

Manually run SQL in mod-users database to add needed attribute update-custom-field.sql

After upgrade

Carole Godfrey
Sobha Duvvuri
Dmytro Tkachenko
Pavlo Smahin


FCFIELDS-9 - Getting issue details... STATUS

mod-login-samlsp-metadata.xml has changedSingle-Sign-Login (SSO) fails. Error message: Validation of received messages enabled, but no signature found on message.Download new sp-metadata.xml from Settings->Tenant->SSO settings->Download metadata, and upload it to IdP.After upgrade

Julian Ladisch


MODLOGSAML-75 - Getting issue details... STATUS


New Apps

  • quickMARC - Lightweight MARC record editing tool. Accessed via Inventory.

New Permissions

  • quickMARC: View, edit
  • Access Status Types: View, edit, create, delete
  • Search: Can search using the Codex with all back-ends

Known Issues

General

  • RMB based database storage modules sometimes does not return all records (RMB-684) when the returned totalRecords property is >= 1000. This affects modules that haven't upgraded to RMB >= 30.2.5.
  • Estimated search result count has a wording that incorrectly suggests it is a precise number ("8081 records found"). Only numbers below 1000 are precise (details: RMB Estimated totalRecords). (WIP FOLIO-2648 - Getting issue details... STATUS )
  • Success status (201 HTTP code) when module upgrade or installation fails (for example database failure). This bug is in many RAML Module Builder based back-end modules (RMB-687) that haven't upgraded to RMB >= 30.2.5. Workaround: Grep the logs for ERROR messages.
  • Purging an RMB based module for a tenant (for example using DELETE /_/proxy/tenants/test/modules/mod-permissions-5.11.3?purge=true API) will result in database errors when reinstalling the module for the same tenant. (RMB-723) Workaround: Restart the module before reinstalling (for example docker restart).
  • Some modules fail in Pgpool-II replication (FOLIO-2447).

Inventory

Search on call number, eye readable in the Holdings and Item segment:

  • When searching on the call number itself then always use wildcard * as right truncation; otherwise will the search result not include results where the given <call number> also has a <call number, prefix>  present. Example: Search: GE77 .F73 2014* in order to find: GE77 .F73 2014 Curriculum Materials Collection. This known issue will be solved when following features are implemented:

Invoices

  • UINV-162 - Getting issue details... STATUS User is not able to search an invoice based on a PO number as one of the tables is not being populated. This relates to displaying related invoices on PO as well, which is a known issue for orders

Orders

  • MODINVOICE-148 - Getting issue details... STATUS Currently the table relating the invoice and PO number is not being populated properly. All invoices do have POL numbers populated properly so related invoice information can be found on the POL but not the PO

  • UIOR-583 - Getting issue details... STATUS When defining order prefixes and suffixes in Settings, all of which contained can contain a '-'. However, when trying to use them in creating a purchase order, the Order app returns an error message that the order number is not valid. A dash (or other non-alpha characters) can't be used in a PO number. Validation must be added to prefix/suffix CRUD to avoid this confusion. 

  • MODFISTO-136 - Getting issue details... STATUS  When selecting an encumbrance transaction in the transaction area the "Awaiting payment" amount for the encumbrance may be incorrect. This is because it does not decrease when the corresponding amounts are expended. However, this does not affect the Budget calculation of "awaiting payment", budget totals are represented correctly.
  • MODORDERS-423 - Getting issue details... STATUS  Unable to open PO when one or more purchase order lines are in a different currency than that of your fiscal year (Generally this will be the same as the system currency found in localization settings unless it was changed during the year)

Automated Patron Blocks

  • Three of the six planned automated patron blocks are being introduced in Goldenrod:
    • Maximum number of items charged out - in Goldenrod
    • Maximum number of lost items - in Goldenrod
    • Maximum outstanding fee/fine balance- in Goldenrod
    • Maximum number of overdue items - planned for Honeysuckle
    • Maximum number of overdue recalls - planned for Honeysuckle
    • Recall overdue by maximum number of days - planned for Honeysuckle
  • The Maximum outstanding fee/fine balance automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs: 
  • The Maximum number of outstanding lost items automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs: 
  • The Maximum number of items charged out automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs: 
  • There is also a user story impacting all automated patron blocks:

Claimed Returned Fees/Fines Suspension

  • Feature planned for Q2 2020 but not completed: UXPROD-2247 - Getting issue details... STATUS
  • The impact is low:
    • Declared lost - If the patron declares the item lost and then says "oops, I just remembered that I returned the item", any lost fees billed would need to be manually waived/cancelled
    • Aged to lost - This is where the big impact would be, except that aged to lost has not been implemented yet so there is no impact
    • Overdue fines from late return (if library has setting in place to charge overdue fines for late return) - Given the item was not actually returned, but claimed returned, there will not be any overdue fines
    • Overdue fines from late renewal (if library has setting in place to charge overdue fines for late renewal) - Overdue fines from a late renewal, before the item was claimed returned, would still be owed (unless the library wanted to waive/cancel them for some reason)

Agreements

ERM-1114 - Getting issue details... STATUS

Duplicating an Agreement including Supplementary Information results in the duplicated Agreement and the original agreement using the same Supplementary Document record. Once this has occurred

  • It is no longer possible to remove the document from either agreement
  • It is no longer possible to delete either agreement
  • Any edits to the supplementary document on one of the agreements will also update the supplementary document on the other agreement (because there is only one document record which is attached to both agreements)

Because of this it is recommended that when duplicating Agreements users should ensure they do not check the "Supplementary Information" option in the the Duplicate Agreement dialogue

Data Import

  • If giving a User Settings (data-import): display list of settings pages as a permission, also assign Settings (Inventory): Display list of settings pages and Settings (Tags): display list of settings pages to avoid error messages. This will be corrected in Honeysuckle
  • Supported in Goldenrod:
    • Import of MARC Bibliographic records, Inventory Instances, Inventory Holdings, and Inventory Items
    • Create and update of the above record types
    • Field mapping profile details for Inventory instances, holdings, and items
    • Performance improvements for retrieving data from Source Record Storage



Post-Release Hotfixes

Hot fix release #1 - RELEASED AT AUGUST 15

Tickets list

Key Summary T Assignee P Resolution development team Reporter
Refresh

Modules list

Project Priority
P1P1 P2P2 P3P3 TBDTBD T:
RAML Module Builder 1 4 0 0 5
data-import-processing-core 0 3 1 0 4
mod-circulation 0 6 0 1 7
mod-circulation-storage 0 0 0 1 1
mod-data-export 1 1 0 0 2
mod-data-import 1 0 0 0 1
mod-feesfines 1 3 0 0 4
mod-finance-storage 0 1 0 0 1
mod-inventory 0 2 0 0 2
mod-inventory-storage 0 11 1 2 14
mod-invoice 0 1 1 0 2
mod-oai-pmh 0 1 0 0 1
mod-orders 0 1 0 0 1
mod-patron-blocks 0 6 0 0 6
mod-pubsub 0 1 0 0 1
mod-quick-marc 0 1 1 0 2
mod-source-record-manager 0 3 0 0 3
mod-source-record-storage 0 1 0 0 1
mod-template-engine 0 1 0 0 1
release 0 2 0 0 2
ui-calendar 0 1 0 0 1
ui-checkin 1 0 0 0 1
ui-circulation 0 1 0 0 1
ui-data-import 0 3 0 0 3
ui-organizations 0 1 0 0 1
ui-quick-marc 0 1 1 0 2
ui-requests 1 1 1 0 3
ui-users 0 1 0 0 1
Total Unique Issues: 6 58 6 4 74
Showing 28 of 28 statistics.
View in Jira

Hot fix release #2 - RELEASED AT SEPTEMBER 17

Tickets list

Key Summary T Assignee P Resolution development team Reporter
Refresh

Modules list

Project Priority
P1P1 P2P2 P3P3 T:
ERM Platform 1 0 0 1
RAML Module Builder 0 4 0 4
data-import-processing-core 0 1 0 1
mod-circulation 0 1 0 1
mod-circulation-storage 0 4 0 4
mod-configuration 0 1 0 1
mod-courses 1 0 1 2
mod-finance 1 0 0 1
mod-inventory 1 0 0 1
mod-inventory-storage 3 3 0 6
mod-login 0 1 0 1
mod-login-saml 0 1 0 1
mod-oai-pmh 1 0 0 1
mod-permissions 0 2 0 2
mod-source-record-storage 0 1 0 1
mod-user-import 0 1 0 1
release 0 1 0 1
ui-checkout 0 1 0 1
Total Unique Issues: 8 22 1 31
Showing 18 of 18 statistics.
View in Jira

Hot fix release #3 - RELEASED AT OCTOBER 10

Tickets list

Key Summary T Assignee P Resolution development team Reporter
Refresh

Modules list

Project Priority
P1P1 P2P2 T:
ERM Platform 1 0 1
mod-circulation 0 1 1
mod-circulation-storage 0 1 1
mod-feesfines 0 1 1
mod-kb-ebsco-java 0 1 1
mod-oai-pmh 0 1 1
mod-source-record-manager 0 1 1
stripes-core 1 0 1
Total Unique Issues: 2 6 8
Showing 8 of 8 statistics.
View in Jira

Hot fix release #4 - RELEASED AT OCTOBER 15

Tickets list

Key Summary T Assignee P Resolution development team Reporter
Refresh

Modules list

Project Priority
P1P1 P2P2 TBDTBD T:
RAML Module Builder 1 0 0 1
mod-configuration 0 2 0 2
mod-inventory-storage 0 2 1 3
mod-permissions 0 2 0 2
mod-users 0 1 0 1
Total Unique Issues: 1 7 1 9
Showing 5 of 5 statistics.
View in Jira

Hot fix release #5 - RELEASED AT NOVEMBER 25

Tickets list

Key Summary T Assignee P Resolution Reporter
Refresh

Modules list

Project Priority
P1P1 P2P2 P3P3 T:
RAML Module Builder 0 3 1 4
mod-circulation 1 0 0 1
mod-kb-ebsco-java 0 2 0 2
mod-pubsub 1 1 0 2
ui-eholdings 0 0 1 1
Total Unique Issues: 2 6 2 10
Showing 5 of 5 statistics.
View in Jira

New Features by Epic (Sub-Project)

epic link Key Summary
Refresh

Closed Bugs

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
Bug Fest 0 0 0 1 0 0 1
Chalmers 0 0 0 0 0 9 9
ERM Platform 4 3 8 0 0 43 58
FOLIO 1 8 12 1 0 7 29
Okapi 2 2 2 0 0 5 11
RAML Module Builder 2 12 6 1 0 14 35
Reporting Tools 0 0 0 0 0 1 1
Stripes 0 0 4 0 0 0 4
UX Product 0 0 0 0 0 2 2
User Experience Design 0 0 1 0 0 0 1
cql2pgjson 0 0 2 0 0 0 2
data-import-processing-core 0 6 2 0 0 0 8
edge-orders 0 0 1 0 0 0 1
folio-service-tools 0 0 1 0 0 0 1
mod-authtoken 1 0 3 0 0 2 6
mod-calendar 0 0 1 0 0 1 2
mod-circulation 7 17 3 4 0 10 41
mod-circulation-storage 0 0 3 4 1 2 10
mod-codex-mock 0 0 0 1 0 0 1
mod-configuration 0 1 0 0 0 0 1
mod-courses 0 0 0 0 0 1 1
mod-customfields 0 1 1 0 0 1 3
mod-data-export 0 5 8 0 0 0 13
mod-data-import 0 2 2 0 0 0 4
mod-di-converter-storage 0 5 0 0 0 0 5
mod-erm-usage 0 0 0 0 0 1 1
mod-erm-usage-harvester 0 0 0 0 0 2 2
mod-feesfines 1 0 0 0 0 2 3
mod-finance 0 2 1 0 0 0 3
mod-finance-storage 0 3 2 0 0 0 5
mod-inventory 0 7 4 2 0 2 15
mod-inventory-storage 0 9 3 20 0 3 35
mod-invoice 0 2 8 0 0 0 10
mod-invoice-storage 0 1 2 0 0 0 3
mod-kb-ebsco-java 0 2 1 0 0 0 3
mod-login 0 2 7 0 0 0 9
mod-login-saml 0 1 0 0 0 0 1
mod-marccat 0 0 0 0 0 8 8
mod-notes 0 0 1 0 1 0 2
mod-oai-pmh 1 9 3 0 0 0 13
mod-orders 0 8 3 0 0 0 11
mod-orders-storage 1 4 1 0 0 0 6
mod-organizations 0 1 0 0 0 0 1
mod-organizations-storage 0 2 0 1 0 0 3
mod-patron 0 0 1 0 0 0 1
mod-patron-blocks 0 5 0 0 0 1 6
mod-permissions 0 2 10 0 0 3 15
mod-pubsub 3 6 2 0 0 0 11
mod-quick-marc 0 0 1 0 0 0 1
mod-sender 1 0 0 0 0 1 2
mod-source-record-manager 0 6 2 0 0 0 8
mod-source-record-storage 1 18 0 0 0 0 19
mod-user-import 0 0 1 1 0 0 2
mod-users 0 0 3 5 0 0 8
mod-users-bl 0 1 8 1 0 0 10
sip2 0 1 0 0 0 0 1
stripes-cli 0 1 1 0 0 0 2
stripes-components 0 0 11 1 0 4 16
stripes-connect 1 0 2 1 0 1 5
stripes-core 0 1 5 0 0 0 6
stripes-data-transfer-components 0 0 1 0 0 0 1
stripes-smart-components 1 7 13 0 0 0 21
stripes-testing 0 0 0 0 0 1 1
ui-calendar 0 0 1 0 0 2 3
ui-checkin 1 0 2 0 0 0 3
ui-checkout 1 3 1 2 0 0 7
ui-circulation 2 4 4 1 0 2 13
ui-courses 2 0 0 0 0 3 5
ui-data-export 1 1 6 0 0 1 9
ui-data-import 2 20 18 1 0 0 41
ui-developer 0 0 1 0 0 0 1
ui-eholdings 0 5 14 2 0 0 21
ui-erm-usage 0 0 0 0 0 1 1
ui-finance 0 3 6 1 0 0 10
ui-finc 0 0 0 0 0 5 5
ui-inventory 2 17 24 5 1 9 58
ui-invoice 0 1 6 1 0 0 8
ui-marccat 0 0 0 0 0 5 5
ui-oai-pmh 0 1 0 0 0 0 1
ui-orders 0 5 14 3 0 0 22
ui-organizations 0 0 10 2 0 0 12
ui-plugin-find-instance 0 0 0 0 0 1 1
ui-plugin-find-user 0 1 1 0 0 0 2
ui-quick-marc 0 1 2 0 0 0 3
ui-receiving 1 3 8 0 0 0 12
ui-requests 1 9 9 3 0 3 25
ui-search 0 0 1 0 0 0 1
ui-servicepoints 0 0 2 0 0 0 2
ui-tags 0 1 1 2 0 0 4
ui-tenant-settings 0 0 7 1 0 1 9
ui-users 7 28 27 8 0 6 76
Total Unique Issues: 47 266 322 76 3 166 880
Showing 91 of 91 statistics.
View in Jira

All Closed Bugs and Stories

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
ARCHIVED: mod-aes 0 0 0 0 0 1 1
Bug Fest 0 0 0 2 0 0 2
Chalmers 0 0 0 0 0 9 9
ERM Platform 4 3 15 2 0 96 120
FOLIO 2 15 16 1 0 7 41
Okapi 2 4 2 0 0 5 13
RAML Module Builder 2 14 6 1 0 14 37
Reporting Tools 0 0 0 0 0 2 2
Stripes 0 0 8 0 0 2 10
UX Product 0 0 0 0 0 2 2
User Experience Design 1 1 4 1 0 1 8
cql2pgjson 0 0 2 0 0 0 2
data-import-processing-core 0 6 4 0 0 0 10
edge-ncip 0 0 2 0 0 0 2
edge-oai-pmh 0 0 3 0 0 0 3
edge-orders 0 0 6 0 0 0 6
edge-patron 0 1 1 0 0 0 2
edge-rtac 0 2 1 0 0 0 3
folio-di-support 0 0 2 0 0 0 2
folio-holdingsiq-client 0 0 2 0 0 0 2
folio-service-tools 0 0 3 0 0 0 3
mod-audit 1 0 0 0 0 0 1
mod-authtoken 1 0 3 0 0 2 6
mod-calendar 0 0 3 0 0 2 5
mod-circulation 8 37 3 4 0 18 70
mod-circulation-storage 1 2 3 4 1 5 16
mod-codex-ekb 0 0 3 0 0 0 3
mod-codex-inventory 0 0 0 0 0 1 1
mod-codex-mock 0 0 0 1 0 0 1
mod-codex-mux 0 0 2 0 0 0 2
mod-configuration 0 2 0 0 0 0 2
mod-courses 0 0 0 0 0 1 1
mod-customfields 0 1 9 0 0 1 11
mod-data-export 0 11 71 0 0 5 87
mod-data-import 0 2 2 0 0 0 4
mod-di-converter-storage 0 8 0 0 0 0 8
mod-email 0 0 1 0 0 1 2
mod-erm-usage 0 0 0 0 0 5 5
mod-erm-usage-harvester 0 0 0 0 0 2 2
mod-event-config 0 0 1 0 0 1 2
mod-feesfines 3 2 1 0 0 5 11
mod-finance 0 3 9 0 0 0 12
mod-finance-storage 0 4 17 0 0 0 21
mod-gobi 0 0 2 0 0 0 2
mod-inventory 0 16 9 2 0 3 30
mod-inventory-storage 1 20 7 20 0 5 53
mod-invoice 0 2 25 0 0 0 27
mod-invoice-storage 0 1 10 0 0 0 11
mod-kb-ebsco-java 0 3 40 0 0 0 43
mod-login 0 2 11 0 0 0 13
mod-login-saml 0 2 1 0 0 0 3
mod-marccat 0 0 0 0 0 8 8
mod-ncip 0 0 3 0 0 0 3
mod-notes 0 0 8 0 1 0 9
mod-notify 1 0 1 1 0 1 4
mod-oai-pmh 2 24 19 0 0 0 45
mod-orders 0 8 22 0 0 0 30
mod-orders-storage 1 5 14 0 0 0 20
mod-organizations 0 1 7 0 0 0 8
mod-organizations-storage 0 2 7 1 0 0 10
mod-password-validator 0 0 4 0 0 1 5
mod-patron 0 1 2 0 0 0 3
mod-patron-blocks 0 6 1 0 0 14 21
mod-permissions 0 2 10 0 0 3 15
mod-pubsub 3 10 2 0 0 0 15
mod-quick-marc 0 1 12 0 0 2 15
mod-rtac 0 1 0 0 0 0 1
mod-sender 1 0 1 0 0 2 4
mod-source-record-manager 0 12 2 0 0 0 14
mod-source-record-storage 1 21 1 0 0 0 23
mod-tags 0 0 2 0 0 0 2
mod-template-engine 0 0 1 0 0 1 2
mod-user-import 0 0 2 1 0 0 3
mod-users 0 1 8 5 0 3 17
mod-users-bl 0 1 10 1 0 1 13
perf-testing 3 11 8 0 0 5 27
release 1 3 1 0 0 57 62
sip2 0 3 0 0 0 0 3
stripes-acq-components 0 0 2 0 0 0 2
stripes-cli 0 1 1 0 0 1 3
stripes-components 0 2 26 2 0 5 35
stripes-connect 1 0 2 1 0 2 6
stripes-core 0 1 7 0 0 1 9
stripes-data-transfer-components 0 0 7 0 0 0 7
stripes-final-form 0 0 0 0 0 1 1
stripes-form 0 0 0 0 0 1 1
stripes-smart-components 1 9 30 0 0 2 42
stripes-testing 0 0 0 0 0 2 2
stripes-util 0 0 0 0 0 1 1
ui-acquisition-units 0 0 2 0 0 0 2
ui-calendar 0 0 1 0 0 3 4
ui-checkin 1 5 2 1 0 2 11
ui-checkout 1 7 2 2 0 2 14
ui-circulation 3 5 9 1 0 8 26
ui-courses 2 0 0 0 0 3 5
ui-data-export 1 1 49 0 0 2 53
ui-data-import 3 41 21 2 0 0 67
ui-developer 0 0 2 0 0 1 3
ui-eholdings 0 6 36 3 0 4 49
ui-erm-usage 0 0 1 1 0 4 6
Total Unique Issues: 64 481 920 94 4 395 1958
Showing 100 of 128 statistics.
Show more

View in Jira

Remaining Open Bugs at Time of Release 

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
ACQ Draft 0 0 0 0 0 1 1
ARCHIVED: edge-resolver 0 0 0 0 0 1 1
ARCHIVED: mod-aes 0 0 0 0 0 6 6
ARCHIVED: ui-search-es 0 2 5 0 0 2 9
Bug Fest 23 18 8 0 0 9 58
Chalmers 0 0 7 1 0 68 76
ERM Platform 20 49 27 8 0 316 420
FOLIO 6 47 60 5 0 132 250
Folio Automation Testing 9 2695 11 0 0 24 2739
LDP Query 0 0 0 0 0 2 2
Okapi 9 18 13 4 0 97 141
RAML Module Builder 4 34 46 0 0 73 157
Reporting App - Back End 9 2 2 0 0 2 15
Reporting App - Front End 4 12 7 0 0 5 28
Reporting Tools 0 0 0 0 0 2 2
Reservoir 1 2 1 0 0 4 8
Service Interaction 0 1 0 0 0 9 10
Stripes 2 10 7 2 0 6 27
Support 1 5 5 0 0 8 19
UI-Serials-Management 0 0 0 0 0 1 1
UX Product 0 0 0 1 0 0 1
User Experience Design 0 0 0 0 0 2 2
Z39.50 4 2 2 0 0 5 13
cql2pgjson 0 0 3 0 0 0 3
data-import-processing-core 13 74 16 2 0 3 108
edge-api-utils 0 0 1 0 0 1 2
edge-caiasoft 0 2 0 0 0 2 4
edge-common 0 2 2 0 0 7 11
edge-common-spring 0 0 0 0 0 2 2
edge-connexion 1 1 1 0 0 7 10
edge-courses 0 0 2 0 0 0 2
edge-dematic 3 6 2 0 0 3 14
edge-fqm 0 2 0 0 0 0 2
edge-inn-reach 5 0 0 1 0 4 10
edge-lti-courses 0 2 0 0 0 0 2
edge-ncip 0 1 0 0 0 1 2
edge-oai-pmh 0 1 1 0 0 3 5
edge-orders 0 2 2 0 0 1 5
edge-patron 2 2 7 0 0 5 16
edge-rtac 1 2 4 1 0 3 11
eslint-config-stripes 0 0 1 0 0 3 4
folio-custom-fields 0 0 1 0 0 1 2
folio-di-support 0 0 0 0 0 1 1
folio-kafka-wrapper-util 0 3 2 0 0 2 7
folio-query-tool-metadata 0 0 1 0 0 0 1
folio-s3-client 0 1 2 0 0 1 4
folio-service-tools 0 0 4 0 0 2 6
folio-spring-base 2 3 5 0 0 14 24
folio-vertx-lib 0 0 0 0 0 14 14
generate-marc-utils 0 3 4 0 0 1 8
isbn-util 0 1 0 0 0 0 1
liquibase-util 0 2 3 0 0 4 9
mod-audit 1 14 12 0 0 11 38
mod-authtoken 1 4 2 0 0 12 19
mod-bulk-operations 5 12 19 0 0 4 40
mod-bulkedit 0 0 0 0 0 1 1
mod-calendar 3 0 0 0 0 7 10
mod-circulation 42 170 67 7 0 43 329
mod-circulation-item 0 0 0 0 0 2 2
mod-circulation-storage 1 23 11