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 timing,
Action required
CommentsContact person,
Related JIRAs
Affected app or moduleWhat has been changed or added that should be noted for this releaseWhat challenges may arise related to this change or additionWhen can the action be taken (before, during or after upgrade)?
If applicable, detail what action(s) must be taken here
Name of user leaving comment: comment on what you encountered or ask a question @mention Contact personUser name of person that can provide additional detail.
Include issue link for bug fix, story or feature that applies
PostgreSQLMinimum required PostgreSQL version is 12installing or upgrading mod-inventory-storage fails with syntax error on "CREATE TRIGGER check_statistical_code_references_on_insert" and other modules fail with "ALTER TYPE ... ADD cannot run inside a transaction block"
Migrate PostgreSQL to version 12 (or a later version) before upgrade; only 12 is tested and recommended

FOLIO-2145 - Getting issue details... STATUS

MODINVSTOR-676 - Getting issue details... STATUS

OkapiLotus version of Okapi (>= v4.13.0) rejects unknown permissionsKiwi version of mod-data-export-spring (1.2.1, 1.2.2) uses
circulation-logs.collection.get
permission without requiring it in ModuleDescriptor. This may fail the installation.

Before upgrading Okapi:

Upgrade mod-data-export-spring to 1.2.3 that has the permissions been fixed.


Adam Dickmeiss 

Julian Ladisch 

MODEXPS-67 - Getting issue details... STATUS

OkapiInteger overflow in version numberOkapi before 4.12.1 and before 4.13.2 fails with an integer overflow on the existing version number 4000001006Before fetching new module descriptors upgrade Okapi to a version >= 4.13.2 (or >= 4.12.2).

Adam Dickmeiss 

OKAPI-1091 - Getting issue details... STATUS

CirculationKafka is requiredconfigure KafkaBefore upgrade: Set KAFKA_PORT, KAFKA_HOST and REPLICATION_FACTOR environment variables for mod-circulation-storage container

Brooks Travis 

UXPROD-3380 - Getting issue details... STATUS

mod-inventoryRequires PostgreSQL configurationOtherwise upgrade fails with "org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections."

Set DB_ environment variables for mod-inventory. For details see RMB readme.

Note: This is about mod-inventory, not mod-inventory-storage!


MODINV-588 - Getting issue details... STATUS

UsersexternalSystemId is unique now.Duplicate externalSystemIds fail the upgrade.  Upgrade error response mentions index name users_externalSystemId_idx_unique. mod-users log mentions actual duplicate externalSystemId.

Before upgrade:
Change all duplicate externalSystemIds.
This SQL lists only the duplicates:
SET search_path TO diku_mod_users;
SELECT left(lower(f_unaccent( jsonb->>'externalSystemId')), 600)
FROM users
GROUP BY 1
HAVING count(*) > 1;

Use User Keyword search to edit the duplicate externalSystemIds until the SQL query result is empty.


Julian Ladisch

MODUSERS-247 - Getting issue details... STATUS

PermissionsRestrictions on what permissions can be added to a user. 

The admin user should have perms.assign.permissions-class of permissions to be able to hand-out permissions that are not owned already. See https://github.com/folio-org/mod-permissions#introduction


If migrating from earlier version mod-permissions, the admin users will automatically be assigned these. This is done in mod-permissions tenant operation itself . 



OrganizationsEDI details have moved to the "Integration detail" accordion. Orgs can now have multiple integration configurationsWhen you first look at an organization record you will not see your EDI details. When you create your first integration for that organization it will be populated with your previously entered EDI details and you will be able to edit those details as needed to save the integration configuration.You will have 2 releases to update your organization integration details. If you have not created an integration for an organization record that previously had EDI details by the Nolana release your EDI details may be lost and you will need to enter them from scratch when adding your first integrationDB: This has been implemented as a UI migration of data because there are technical restrictions that prevented us from using the BE to populate these details on the user's behalf.

UIORG-188 - Getting issue details... STATUS

Single Sign On (SSO)

Browser vendors (Chrome, Firefox, Edge) restrict cookie usage across different sites resulting in SSO failure with "CSRF attempt detected" error message.

Front-end host name (Stripes) and back-end host name (Okapi) must belong to the same site.When defining host names.Not applicable if mod-login-saml (SSO) is not used.
InventoryItems with invalid statistical code ids (non-existing or non-UUID).
They are rejected with one of these error messages:
  • statistical code doesn't exist: eeb7fef6-bd65-4cd8-81bc-1c2d91551b94: foreign key violation in statisticalCodeIds array of item with id=9428231b-dd31-4f70-8406-fe22fbdeabc2
  • invalid input syntax for type uuid: "foo"

If there is an invalid statistical code id the migration neither fails nor cleans up the invalid id.

However, an item that was accepted in Kiwi can no longer been created in Lotus. Changing the list of statistical codes of an existing item fails unless all statistical codes exist; updating an item without changing the list of statistical code ids (= only changing other properties) always succeeds even if it contains an invalid statistical code id.

Before or after the migration:

Manually clean up invalid statistical code ids in all items.

Manually add missing statistical codes in Settings/Inventory/Statistical codes.


Call number and subject browse

Inventory search supports now browse functionality by call number and subject.

The call number browse is based on the item record's shelving order and it covers browsing LC, Dewey Decimal, NLM, SuDoc and Local call numbers.

The subject browse is based on  the Subject field of inventory instance records. 

Browse functionality requires:

  • granting Call number browse: View permissions  and Subject browse: View permissions
  • Item's shelving order field need to be populated (by running migration scripts that are part of mod-inventory storage)
  • full re-index with recreating indexes 
  1. After deploying latest version of mod-inventory-storage run migration scripts that will update shelving order on the item record.  To start migration use  POST /inventory-storage/migrations/jobs with request body:

    {"migrations": ["itemShelvingOrderMigration"]}
  2.  Once the migration script competes full re-index with the property  "recreateIndex" set to true
Search

Inventory search supports now MARC Authorities search and browse functionality for call number and subjects

Inventory search support search on All data properties across all three record types. 

mod-search indices will need to recreated as described here

This search is a powerful tool, but can have implications on performance.

IMPORTANT: See documentation here.

During the upgrade process.


The search option need to be enabled in the given FOLIO environment. See the mod-search README for details on how to configure.





UsersPermissions changes to ui-users.loans.all:
  • Subpermission changes: remove ui-users.loans.edit and add ui-users.loans.change-due-date
  • Remove from ui-users.loans.all the ability to:
    • declare an item lost
    • mark an item claim returned
    • mark a claim returned item missing
    • anonymize a user's loans
    • renew an item through override 
  • Change the display name (and associated translations) for ui-users.loans.all to "Users: User loans view, change due date, renew"
  • removing ui-users.loans.edit should have no effect 
  • For users who currently have ui-users.loans.all assigned, if you need them to be able to continue to declare item lost, mark item claim returned, mark claim returned item missing, anonymize user loan, renew an item through override, you will need to assign those users that functionality with the additional individual permission for the functionality
Assigning additional permissions to end users if needed could be done prior to or after the Lotus upgradeDiscussed at the RA SIG on 7-26-2021 - 2021-07-26 Resource Access Meeting Notes

Erin Nettifee 

UIU-2256 - Getting issue details... STATUS

Requests - title levelThe data migration necessary for title level requests is included in Lotus (see this wiki page for details). A fully functional release of title level requests will not be available until Morning Glory. 

There will be references to title level and title level requests in the Requests detail pane that cannot be suppressed or removed at this point. They will make sense and be functional with Morning Glory.

This migration includes breaking changes in the requests schema. Among other changes, fields "requestLevel" and "instanceId" are now mandatory. Affected modules are mod-circulation, mod-circulation-storage and edge-patron. Please see this page for more information. 



Requests- title level data migration

In Request details where a placeholder ID 00000000-0000-4000-8000-000000000000 is used to replace a missing holdingsRecordId and/or instanceId (to allow for data migration to complete), the following occurs:

existing item + existing holdings + existing instance = page loads normally
deleted item + existing holdings + existing instance = page breaks, something went wrong error
deleted item + deleted holdings + deleted instance = page breaks, something went wrong error




Stephanie Buck 
Export Manager | AcquisitionsAcquisitons has implemented a feature for exporting orders in EDIFACT format. In order to do this you must add  an "Integration" to the organization you would like to send EDI files to.For the EDIFACT orders export to work reliably your environment must have ONLY 1 instance of mod-data-export-spring deployed.

This should be considered at time of upgrade if you plan to export orders in edifact format with the Lotus release.

It can be adjusted post upgrade but you will likely have failed exports in the mean time and there is no easy way to "Re-export" orders in this release.

We did not have capacity to resolve this issue in Lotus so updates will be made for a future release

Dennis Bridges 

MODEXPS-75 - Getting issue details... STATUS

MODEXPS-81 - Getting issue details... STATUS

OAI-PMH

mod-oai-pmh  supports only one concurrent full harvest.


Recommended edge and mod-oai-pmh module settings that prevents harvests end prematurely on a larger data sets:

edge-oai-pmh memory settings: -Xmx952m

mod-oai-pmh ENV recommendation: 

      { "name": "DB_QUERYTIMEOUT", "value": "2700000" },
      { "name": "DB_MAXPOOLSIZE", "value": "20" }


Starting with Lotus HF1 mod oai-pmh provides APIs for monitoring the harvesting process as documented in the READ.ME file.


Results of the performance tests when running multiple full harvests concurrently can be found here


The settings change  will required restarting the module



The relevant module descriptors will be updated for Morning Glory release

mod-quickmarcDisable High Availability (HA) as it the module is not reliable when HA is set. 


mod-kb-ebsco-java,

mod-pubsub

In a multi-tenant environment the module had used a wrong tenant id to calculate the checksum that was stored in the md5sum column of liquibase database table databasechangelog for previous flower releases.Upgrade from Kiwi to Lotus fails with this liquibase checksum validation failure:
liquibase.exception.ValidationFailedException: Validation Failed: 5 change sets
If upgrade fails with this validation failure then replace md5sum checksum in databasechangelog database table; values are tenant specific and must be taken from the error messages in the logs. Example: MODPUBSUB-240

Viacheslav Kolesnyk : during upgrading a tenant for a Lotus we have encountered liquibase checksums validation failure which is not reproducible locally.

Viacheslav Kolesnyk 

Varun Javalkar 

MODKBEKBJ-656 - Getting issue details... STATUS

MODPUBSUB-240 - Getting issue details... STATUS

edge-inn-reach, mod-inn-reachThese modules are no longer part of platform-complete.
If not used disable them for the tenant and undeploy the module.
https://github.com/folio-org/platform-complete/pull/1985

New Apps

MARC Authority: For libraries that plan to manage MARC authority records in FOLIO. Hosting providers, please ask your customers whether this app should be enabled. Lotus capabilities are 

  • Create MARC authority records via Data import 
  • Update MARC authority records via Data import 
  • Edit MARC authority record via quickMARC 
  • View MARC authority record source 
  • Basic/Advanced Search 
  • Browse Authority headings and references 

Removed Apps

  • INN-Reach (will be released as a standalone deployment for use with Lotus, but we are awaiting production certification from Innovative before we consider including it in Platform Complete again)

Permissions Updates

AppNew PermissionsDeprecated PermissionsProduct Owner
MARC authority app 

View MARC authority record 

Edit MARC authority record 

quickMARC: View, edit MARC authority record 


Settings - Title level requestsSettings (circ): Title level request edit
Agreements

Settings (Agreements): Can view app settings

Settings (Agreements): Can view and edit app settings

These new settings give view/edit permissions to a set of "app settings" via the Settings. As of Lotus, the available app settings are to setup options for storing documents uploaded to the Agreements module in database (default) or S3 storage


Owen Stephens 
Licenses

Settings (Licenses): Can view app settings

Settings (Licenses): Can view and edit app settings

These new settings give view/edit permissions to a set of "app settings" via the Settings. As of Lotus, the available app settings are to setup options for storing documents uploaded to the Licenses module in database (default) or S3 storage


InvoicesInvoice: Cancel invoicesNone
AppChanged Permissions

Action required

Contact person,
Related JIRAs

Data ImportData import: all permissions

Remove "Settings (Data import): Can view, create, edit, and remove" from roles and users that don't need to change the settings.

In Kiwi there was a permission bug: To use data import the settings permission was required. This has been fixed for Lotus, therefore the permission that had been added as a workaround should be removed now.

Ann-Marie Breaux

UIDATIMP-1040 - Getting issue details... STATUS

Known Issues

General

AppKnown issueWorkaroundJIRA issueProduct Owner
RequestsRequests app results/filters columns are not sorting properly, descending or ascending. This should be addressed in Morning Glory. There is no workaround at this time. 

UIREQ-750, RMB-906

RequestsAfter opening the Request details pane, an error message appears. This is related to the hold clearance report and is related to large data sets. It seems the report is not adding current actions to the report. This is partially addressed by adding indexes in the DB

CIRCSTORE-336

RequestsHold clearance report times out with large data sets.

CIRC-1517

Brooks Travis 
Title level request data migrationThe migration process failed when it could not determine holdingsRecordId and/or instanceId for a requestLotus HF1 fixes this issue. If migration process fails to determine holdingsRecordId and/or instanceId for a request, a default UUID 00000000-0000-4000-8000-000000000000 is used as a placeholder value
Request detail records with a placeholder value may result in broken links (existing item + deleted holdings + deleted instance = page loads normally with broken links) causing the page to continuously spin. This will be fixed in Morning Glory by sending to an error page

CIRCSTORE-340

UIREQ-783

Stephanie Buck 
AgreementsOn adding a tag to an agreement line, the tag count is not immediately updatedRefreshing the page or closing and re-opening the agreement line view will lead the tag count to refreshing

ERM-2066 - Getting issue details... STATUS

Owen Stephens 
AgreementsTwo new Supplementary Properties are created by default on upgrading the module "Author Identification" and "Does this Agreement Support Publishing". While these properties will not cause any harm or affect the operation of the application, they are probably not required by most/all institutionsDelete these supplementary properties immediately after upgrade

ERM-2222 - Getting issue details... STATUS

Owen Stephens 
Inventory

Instances added in any release up to Iris (R1 2021) that hasn't been updated since then, does not have "_version" field that would result in error ("NumberFormatException: null") when trying to overlay such Instance via Data Import in Lotus GA.

This bug has been fixed in Lotus HF#1 and all later releases.

Fixed in Lotus HF#1 and all later releases.

Workaround needed for Lotus GA:

Add a _version property with a number to all instances without a _version property. 

  • Check if mod-inventory-storage contains such records, execute 
select count ( id ) from <tenant>_mod_inventory_storage."instance" where (jsonb->>'_version') is null;
  • If request above returns number other then 0, execute 
update <tenant>_mod_inventory_storage."instance" set created_by = created_by where (jsonb->>'_version') is null;

Existing trigger would set the version for each Instance that does not have this property 

MODINV-684 - Getting issue details... STATUS

Ann-Marie Breaux 
InventorySEVERE: loadDbSchema loadDbSchema(): Table instance_holdings_item_view NOT FOUND in logIgnore. RMB should suppress this log message for views but it doesn't.

RMB-909 - Getting issue details... STATUS MODINVSTOR-929 - Getting issue details... STATUS

Inventory/Single Record ImportWhen importing a Single record using the Import button in Inventory's action menu, then an instance is created. But if the user then use the 'back' button in the browser, a duplicate import of the same record is createdDo not use the 'back' button.

UIIN-2197 - Getting issue details... STATUS

Charlotte Whitt 
Inventory/TagsCannot add tags to Instance when unlinked preceding/succeeding titles present (in a source = FOLIO instance with preceding/succeeding not linked to another FOLIO instance or in a source = MARC instance with preceding/succeeding data from the SRS MARC 780/785 fields)None

UIIN-2084 - Getting issue details... STATUS

MODINV-674 - Getting issue details... STATUS

Ann-Marie Breaux 
Data importA very large job profile can be created in Settings (Data import), but then errors when the user tries to edit it.Break the job into multiple smaller jobs

UIDATIMP-1166 - Getting issue details... STATUS

Ann-Marie Breaux 
Data importLogs for Inventory Single Record Imports do not always show the details for the imported recordRun a one-time script to set the "order" field of the SRS record. See more details here: Script for setting the SRS record "order" field so that Inventory Single Record Imports do not display blank log information

UIDATIMP-1136 - Getting issue details... STATUS

MODSOURMAN-422 - Getting issue details... STATUS

Ann-Marie Breaux 
Data importPermission "Data import: All permissions" is missing permission "data-import.fileExtensions.get"Corrected in Morning Glory. For now, the missing permission can be manually added to a user as needed. 

UIDATIMP-1193 - Getting issue details... STATUS

Ann-Marie Breaux 
Data importMARC-to-Instance match, followed by an Update MARC Bib action, causes import job to hang and never finish.Use a profile with MARC-to-Instance match followed by Update Instance action, or use a profile with MARC-to-MARC match followed by Update MARC Bib action. In Morning Glory, a job constructed as MARC-to-Instance, then Update MARC Bib action will not work, but will finish with an error instead of getting stuck.

MODSOURCE-509 - Getting issue details... STATUS

MODSOURCE-528 - Getting issue details... STATUS

Ann-Marie Breaux 
Circulation logWhen an item record is deleted, the item barcode remains active in the Circulation log. An error occurs if a user clicks on an item barcode and the item has been deleted. There is no workaround at this time.

UXPROD-3738 - Getting issue details... STATUS

Stephanie Buck 
Export ManagerProblems with scheduling bursar transfers and intermittent issues with manual exports .There is no workaround at this time.  The fix will be available in the Morning glory release

MODEXPW-172 - Getting issue details... STATUS MODEXPS-115 - Getting issue details... STATUS

FinanceOptimistic locking is causing transaction processing to fail when older transactions without version numbers are processed. 

Optimistic locking should be disabled for the finance module

  • ALTER TABLE {tenant}_mod_finance_storage.transaction DISABLE TRIGGER set_transaction_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.budget DISABLE TRIGGER set_budget_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.budget_expense_class DISABLE TRIGGER set_budget_expense_class_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.expense_class DISABLE TRIGGER set_expense_class_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.fiscal_year DISABLE TRIGGER set_fiscal_year_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.fund DISABLE TRIGGER set_fund_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.fund_type DISABLE TRIGGER set_fund_type_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.group_fund_fiscal_year DISABLE TRIGGER set_group_fund_fiscal_year_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.groups DISABLE TRIGGER set_groups_ol_version_trigger;
  • ALTER TABLE {tenant}_mod_finance_storage.ledger DISABLE TRIGGER set_ledger_ol_version_trigger;

MODFISTO-340 - Getting issue details... STATUS

Dennis Bridges 


Acquisitions

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Notes on functionality

Optimistic locking has been enabled for inventory instances, holdings records, and items (Optimistic locking proposal, UXPROD-1752, MODINVSTOR-845).

Post-Release Hotfixes

Hot fix release #1 - RELEASED AT JUNE 15

Tickets list

Key Summary T Assignee P Resolution Reporter
Loading...
Refresh

Modules list


Project Priority
Showing 0 of 0 statistics.
View in Jira

Hot fix release #2 - RELEASED AT JULY 8

Tickets list

Key Summary T Assignee P Resolution Reporter
Loading...
Refresh

Modules list


Project Priority
Showing 0 of 0 statistics.
View in Jira

Hot fix release #3 - RELEASED ON AUGUST 12

Tickets list

Key Summary T Assignee P Resolution Reporter
Loading...
Refresh

Modules list


Project Priority
Showing 0 of 0 statistics.
View in Jira

New Features by Epic (Sub-Project)

Key Summary
Loading...
Refresh

Closed Bugs

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
ACQ Draft 0 0 0 0 0 1 1
ARCHIVED: ui-search-es 0 0 0 0 0 1 1
Bug Fest 5 5 3 0 0 7 20
ERM Platform 2 0 0 0 0 28 30
FOLIO 1 6 5 0 0 25 37
Folio Automation Testing 0 7 2 0 0 4 13
Okapi 2 0 1 0 0 10 13
RAML Module Builder 0 1 1 0 0 8 10
Reporting App - Front End 0 0 0 0 0 3 3
Reservoir 0 0 0 0 0 1 1
Stripes 0 0 0 0 0 1 1
Support 1 3 1 0 0 3 8
User Experience Design 0 0 0 0 0 1 1
Z39.50 0 0 0 0 0 1 1
data-import-processing-core 2 16 4 0 0 0 22
edge-caiasoft 0 1 0 0 0 1 2
edge-common 0 0 0 0 0 2 2
edge-connexion 0 0 0 0 0 3 3
edge-dematic 0 1 0 0 0 0 1
edge-inn-reach 3 0 0 1 0 2 6
edge-patron 0 1 2 0 0 0 3
folio-kafka-wrapper-util 0 1 0 0 0 0 1
folio-service-tools 0 0 0 0 0 1 1
folio-spring-base 0 0 0 0 0 2 2
folio-vertx-lib 0 0 0 0 0 6 6
generate-marc-utils 0 1 1 0 0 0 2
liquibase-util 0 0 2 0 0 1 3
mod-audit 0 2 0 0 0 0 2
mod-authtoken 1 1 0 0 0 5 7
mod-calendar 0 0 0 0 0 2 2
mod-circulation 11 39 15 1 0 19 85
mod-circulation-storage 0 1 0 0 0 2 3
mod-configuration 0 0 1 0 0 5 6
mod-copycat 0 1 0 0 0 2 3
mod-data-export 0 7 4 0 0 0 11
mod-data-export-spring 4 8 1 0 0 2 15
mod-data-export-worker 1 7 3 0 0 1 12
mod-data-import 1 10 7 0 0 0 18
mod-di-converter-storage 0 0 5 0 0 0 5
mod-email 0 0 0 0 0 1 1
mod-erm-usage 0 0 0 0 0 2 2
mod-erm-usage-harvester 0 1 0 0 0 6 7
mod-eusage-reports 3 1 0 0 0 2 6
mod-feesfines 0 1 4 0 0 2 7
mod-finance 1 1 0 0 0 0 2
mod-finance-storage 3 1 3 0 1 0 8
mod-gobi 0 1 1 0 0 0 2
mod-graphql 0 0 0 0 0 4 4
mod-harvester-admin 0 1 0 0 0 0 1
mod-idm-connect 0 0 0 0 0 2 2
mod-inn-reach 10 7 0 0 0 3 20
mod-inventory 8 9 6 1 0 3 27
mod-inventory-storage 2 5 7 1 0 9 24
mod-inventory-update 0 5 3 0 0 0 8
mod-invoice 6 14 7 1 0 1 29
mod-invoice-storage 0 1 0 0 0 0 1
mod-kb-ebsco-java 0 0 5 0 0 2 7
mod-login 0 0 1 0 0 4 5
mod-login-saml 0 3 3 0 0 5 11
mod-notes 0 2 7 0 0 1 10
mod-notify 0 1 1 0 0 3 5
mod-oa 0 0 0 0 0 1 1
mod-oai-pmh 0 4 4 0 0 0 8
mod-orders 0 8 7 0 0 3 18
mod-orders-storage 2 2 2 0 0 0 6
mod-password-validator 0 0 0 0 0 2 2
mod-patron 1 3 1 0 0 1 6
mod-patron-blocks 4 2 0 0 0 2 8
mod-permissions 2 4 1 0 0 6 13
mod-pubsub 3 0 2 0 0 3 8
mod-quick-marc 3 8 4 0 0 0 15
mod-remote-storage 0 2 0 0 0 0 2
mod-rtac 0 2 1 0 0 0 3
mod-search 0 10 9 1 0 3 23
mod-source-record-manager 4 20 20 0 0 1 45
mod-source-record-storage 7 16 6 0 0 0 29
mod-tags 1 3 1 0 0 2 7
mod-template-engine 0 0 3 0 0 0 3
mod-user-import 0 4 1 0 0 3 8
mod-users 0 1 1 1 0 1 4
mod-users-bl 0 1 0 0 0 0 1
rancher 1 3 0 0 0 9 13
sip2 0 1 0 0 0 0 1
stripes-acq-components 0 2 3 0 0 1 6
stripes-cli 1 0 1 0 0 0 2
stripes-components 0 5 14 0 0 13 32
stripes-connect 0 0 1 0 0 0 1
stripes-core 0 1 4 0 0 0 5
stripes-data-transfer-components 1 0 1 0 0 0 2
stripes-smart-components 1 2 8 1 0 4 16
stripes-testing 0 0 0 0 0 1 1
stripes-webpack 0 0 0 0 0 2 2
ui-acquisition-units 0 0 0 1 0 1 2
ui-bulk-edit 1 1 6 0 0 0 8
ui-calendar 0 3 1 5 0 1 10
ui-checkin 0 1 3 0 0 0 4
ui-checkout 0 2 4 0 0 3 9
ui-circulation 0 3 16 2 0 2 23
ui-circulation-log 0 1 0 0 0 1 2
ui-data-export 0 1 2 0 0 0 3
Total Unique Issues: 117 409 377 36 3 329 1271
Showing 100 of 128 statistics.
View in Jira

All Closed Bugs and Stories

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
ACQ Draft 0 0 0 0 0 1 1
ARCHIVED: ui-search-es 0 0 0 0 0 1 1
Bug Fest 5 5 3 0 0 7 20
Chalmers 0 0 1 0 0 0 1
ERM Platform 4 0 3 0 0 57 64
FOLIO 1 13 5 0 0 31 50
Folio Automation Testing 0 8 30 1 0 6 45
Okapi 2 1 1 0 0 17 21
RAML Module Builder 0 1 3 0 0 20 24
Reporting App - Back End 0 5 1 0 0 0 6
Reporting App - Front End 0 1 1 1 0 5 8
Reservoir 0 12 5 0 0 1 18
Stripes 0 0 2 0 0 1 3
Support 1 3 1 0 0 3 8
User Experience Design 0 0 5 0 0 2 7
Z39.50 0 0 1 0 0 3 4
data-import-processing-core 2 16 15 0 0 0 33
edge-caiasoft 0 1 2 0 0 1 4
edge-common 0 0 0 0 0 3 3
edge-common-spring 0 0 2 0 0 0 2
edge-connexion 0 0 0 0 0 3 3
edge-dematic 0 1 0 0 0 1 2
edge-inn-reach 5 1 0 2 0 2 10
edge-oai-pmh 0 0 2 0 0 0 2
edge-patron 0 1 4 0 0 1 6
edge-search-srs 0 0 1 0 0 0 1
folio-custom-fields 0 0 1 0 0 0 1
folio-di-support 0 0 1 0 0 0 1
folio-holdingsiq-client 0 0 2 0 0 0 2
folio-kafka-wrapper-util 0 2 0 0 0 0 2
folio-service-tools 0 0 1 0 0 1 2
folio-spring-base 0 2 4 0 0 4 10
folio-vertx-lib 0 0 0 0 0 8 8
generate-marc-utils 0 1 2 0 0 0 3
liquibase-util 0 0 3 0 0 1 4
mod-audit 0 3 0 0 0 1 4
mod-authtoken 1 5 1 0 0 8 15
mod-bulkedit 0 0 5 0 0 0 5
mod-calendar 0 0 0 0 0 2 2
mod-circulation 11 41 19 1 0 55 127
mod-circulation-storage 0 4 0 0 0 6 10
mod-codex-ekb 0 0 1 0 0 0 1
mod-codex-mux 0 0 1 0 0 0 1
mod-configuration 0 0 1 0 0 6 7
mod-copycat 0 1 0 0 0 2 3
mod-data-export 0 8 20 0 0 0 28
mod-data-export-spring 4 12 8 0 0 2 26
mod-data-export-worker 1 15 20 0 0 1 37
mod-data-import 1 16 16 0 0 0 33
mod-di-converter-storage 0 0 14 0 0 0 14
mod-email 0 0 0 0 0 1 1
mod-erm-usage 0 0 0 0 0 2 2
mod-erm-usage-harvester 0 1 0 0 0 6 7
mod-eusage-reports 4 2 0 1 0 2 9
mod-feesfines 0 3 4 0 0 2 9
mod-finance 1 2 2 0 0 0 5
mod-finance-storage 3 3 5 0 1 1 13
mod-gobi 0 3 3 0 0 0 6
mod-graphql 0 0 0 0 0 6 6
mod-harvester-admin 0 1 0 0 0 0 1
mod-idm-connect 0 0 0 0 0 3 3
mod-inn-reach 19 43 7 18 0 6 93
mod-inventory 9 14 33 1 0 6 63
mod-inventory-storage 3 13 19 1 0 9 45
mod-inventory-update 0 5 3 0 0 0 8
mod-invoice 6 16 9 1 0 1 33
mod-invoice-storage 0 1 1 0 0 0 2
mod-kb-ebsco-java 0 0 16 1 0 3 20
mod-login 0 0 1 0 0 6 7
mod-login-saml 0 4 3 0 0 5 12
mod-ncip 0 1 0 0 0 1 2
mod-notes 0 2 19 0 0 1 22
mod-notify 0 1 1 0 0 3 5
mod-oa 0 0 0 0 0 3 3
mod-oai-pmh 0 8 10 0 0 0 18
mod-orders 0 10 15 0 0 4 29
mod-orders-storage 2 5 9 0 0 1 17
mod-organizations 0 0 1 0 0 0 1
mod-organizations-storage 0 0 0 1 0 0 1
mod-password-validator 0 0 3 0 0 2 5
mod-patron 1 5 4 0 0 2 12
mod-patron-blocks 4 2 0 0 0 3 9
mod-permissions 2 4 1 0 0 11 18
mod-pubsub 3 0 2 0 0 3 8
mod-quick-marc 3 8 13 0 0 1 25
mod-remote-storage 0 3 1 0 0 1 5
mod-rtac 0 2 2 0 0 0 4
mod-search 0 17 59 1 0 3 80
mod-source-record-manager 4 26 52 0 0 1 83
mod-source-record-storage 7 18 25 0 0 0 50
mod-tags 1 3 2 0 0 2 8
mod-template-engine 0 0 3 0 0 0 3
mod-user-import 0 4 1 0 0 4 9
mod-users 0 1 1 2 0 1 5
mod-users-bl 0 2 0 0 0 6 8
perf-testing 0 2 2 0 0 16 20
rancher 1 8 4 0 0 12 25
sip2 0 3 0 0 0 3 6
stripes-acq-components 0 5 15 1 0 1 22
stripes-cli 1 0 1 0 0 1 3
Total Unique Issues: 140 636 1089 75 3 640 2583
Showing 100 of 150 statistics.
View in Jira

Remaining Open Bugs at Time of Release 

Project Priority
P1P1 P2P2 P3P3 P4P4 P5P5 TBDTBD T:
ARCHIVED: edge-resolver 0 0 0 0 0 1 1
ARCHIVED: ui-search-es 0 0 1 0 0 0 1
Bug Fest 18 13 5 0 0 1 37
Chalmers 0 0 2 0 0 33 35
ERM Platform 7 24 12 4 0 153 200
FOLIO 0 15 39 2 0 47 103
Folio Automation Testing 7 2684 7 0 0 16 2714
Okapi 2 3 6 2 0 40 53
RAML Module Builder 1 3 15 0 0 40 59
Reporting App - Back End 2 2 2 0 0 1 7
Reporting App - Front End 1 11 7 0 0 1 20
Reservoir 1 2 1 0 0 3 7
Service Interaction 0 1 0 0 0 9 10
Stripes 1 6 4 2 0 1 14
Support 0 1 1 0 0 5 7
UI-Serials-Management 0 0 0 0 0 1 1
Z39.50 0 1 2 0 0 3 6
cql2pgjson 0 0 3 0 0 0 3
data-import-processing-core 3 29 9 2 0 3 46
edge-api-utils 0 0 1 0 0 1 2
edge-caiasoft 0 1 0 0 0 0 1
edge-common 0 2 1 0 0 5 8
edge-connexion 0 0 1 0 0 2 3
edge-courses 0 0 2 0 0 0 2
edge-dematic 0 3 0 0 0 2 5
edge-fqm 0 2 0 0 0 0 2
edge-inn-reach 2 0 0 0 0 2 4
edge-lti-courses 0 2 0 0 0 0 2
edge-ncip 0 1 0 0 0 1 2
edge-oai-pmh 0 0 0 0 0 2 2
edge-orders 0 2 1 0 0 1 4
edge-patron 2 0 4 0 0 4 10
edge-rtac 1 1 2 1 0 3 8
eslint-config-stripes 0 0 0 0 0 3 3
folio-custom-fields 0 0 0 0 0 1 1
folio-di-support 0 0 0 0 0 1 1
folio-kafka-wrapper-util 0 2 1 0 0 2 5
folio-query-tool-metadata 0 0 0 0 0 1 1
folio-s3-client 0 1 2 0 0 1 4
folio-service-tools 0 0 4 0 0 1 5
folio-spring-base 2 2 5 0 0 11 20
folio-vertx-lib 0 0 0 0 0 8 8
generate-marc-utils 0 1 2 0 0 1 4
isbn-util 0 1 0 0 0 0 1
liquibase-util 0 2 1 0 0 3 6
mod-audit 0 5 0 0 0 5 10
mod-authtoken 0 2 1 0 0 3 6
mod-bulk-operations 5 11 19 0 0 4 39
mod-bulkedit 0 0 0 0 0 1 1
mod-calendar 3 0 0 0 0 5 8
mod-circulation 18 50 28 2 0 6 104
mod-circulation-item 0 0 0 0 0 2 2
mod-circulation-storage 1 14 5 0 0 5 25
mod-codex-inventory 0 0 1 1 0 0 2
mod-codex-mux 0 0 2 0 0 0 2
mod-configuration 0 0 1 1 0 4 6
mod-consortia 0 3 0 0 0 0 3
mod-courses 0 7 0 0 0 3 10
mod-customfields 0 0 2 0 0 0 2
mod-data-export 3 11 11 1 0 2 28
mod-data-export-spring 3 10 8 3 0 4 28
mod-data-export-worker 7 57 44 1 0 9 118
mod-data-import 6 22 11 1 0 7 47
mod-data-loader 0 0 2 0 0 0 2
mod-di-converter-storage 3 13 1 2 0 1 20
mod-ebsconet 1 3 2 0 0 1 7
mod-email 1 0 1 0 0 0 2
mod-entities-links 1 12 16 0 0 3 32
mod-erm-usage 0 2 0 0 0 4 6
mod-erm-usage-harvester 1 1 1 0 0 6 9
mod-eusage-counter 0 0 1 0 0 6 7
mod-eusage-reports 1 0 0 0 0 4 5
mod-feesfines 0 11 3 2 0 1 17
mod-finance 3 8 8 3 0 0 22
mod-finance-storage 9 19 4 1 0 6 39
mod-fqm-manager 0 3 7 0 0 1 11
mod-gobi 1 5 6 1 0 1 14
mod-graphql 1 2 0 1 0 1 5
mod-harvester-admin