Q2 2020 Hot Fix approve log
- Oleksii Petrenko
Owned by Oleksii Petrenko
| # | Date | Issue | PO | Development Team | Description |
|---|---|---|---|---|---|
| 1 | 28-Jul-20 | MDEXP-247 | Concorde | I have a hotfix for https://folio-org.atlassian.net/browse/MDEXP-247 that was discovered yesterday. It is data migration issue related to the existing default mapping profile. We have the fix ready and verified and awaiting the approval for the release. Please approve. | |
| 2 | 29-Jul-20 | MDEXP-253 | Concorde | another request for the mod-data-export release approval. While fixing MDEXP-247 we introduced another issue that was just fixed in https://folio-org.atlassian.net/browse/MDEXP-253. | |
| 3 | 31-Jul-20 | MODOAIPMH-202 | Gulfstream | Could you please approve the hotfix for OAI-PMH, which allows to have more than one mod-oai-pmh module on the environment without breaking the flow and is supposed to speed up each first request to oai-pmh endpoint from the sequence of requests? Here is a ticket for it https://folio-org.atlassian.net/browse/MODOAIPMH-202, fix release version 3.1.0. It goes in pair with https://folio-org.atlassian.net/browse/MODINVSTOR-536 from Inventory, which was released in 19.3.0 version of mod-inventory-storage | |
| 4 | 4-Aug-20 | MODFISTO-125 | Thunderjet | https://folio-org.atlassian.net/browse/MODFISTO-125 - Invoices can not be completed (Paid) because of encumbrance bug. | |
| 5 | 4-Aug-20 | UIORGS-193 | Thunderjet | https://folio-org.atlassian.net/browse/UIORGS-193 - Unable to add additional accounts to Organization records. These fixes are ready and awaiting release, just need approval if possible | |
| 6 | 5-Aug-20 | MODDICORE-75 | Folijet | This is a bug we just discovered recently, but will be a significant issue for libraries using Data Import in Goldenrod. https://folio-org.atlassian.net/browse/MODDICORE-75. If there are two 856 (eAccess) fields in the MARC record, the two URLs are smushed into the same Electronic access field in the holdings record, making the URL unuseable. It's fine in the Instance, but a problem in the Holdings record. We're working on the fix right now. OK to include as a hotfix? | |
| 7 | 5-Aug-20 | MODSOURMAN-333 | Folijet | These are 2 more possible Data Import hotfixes that correct problems with the SRS 999 field (which holds the SRS and Instance UUIDs). It would be great to have as hotfixes, so that we don't perpetuate the problem any longer than necessary. https://folio-org.atlassian.net/browse/MODSOURMAN-333: When creating instances from an imported MARC file that already has a 999 ff field, the newly-created 999 field is wrong | |
| 8 | 5-Aug-20 | MODSOURCE-175 | Folijet | https://folio-org.atlassian.net/browse/MODSOURCE-175: New 999 $s (SRS UUID) is created when an exported file is re-imported to update an instance | |
| 9 | 5-Aug-20 | MODORDERS-416 | Thunderjet | I have a hotfix releases prepared for the following issue: https://folio-org.atlassian.net/browse/MODORDERS-416 - Can not update multiple purchase order lines when paying invoice, causing payment to Fail for multi line purchase orders. There is really no acceptable workaround for this. This fix is ready and awaiting release, just need approval if possible. | |
| 10 | 7-Aug-20 | CIRC-850 | Core: Functional | Folks at index data discovered an issue with scheduled tasks in circulation that meant that Okapi became starved of available network connections and has to be restarted in order for it to communicate with circulation (see https://folio-org.atlassian.net/browse/CIRC-850 for more information) @malc has requested that this be back ported to Goldenrod as it could present a significant operational issue. @cate asked me to request approval on her and @malc behalf from this group. Is it acceptable to back port this to Goldenrod? Please do ask any questions you may have about the issue. | |
| 11 | 7-Aug-20 | MODINVOICE-191 | Thunderjet | Dennis is on vacation, so I'm here to ask for permission for a couple Invoicing hotfixes for Goldenrod: https://folio-org.atlassian.net/browse/MODINVOICE-191 resolves a problem where batch vouchers error rather than completing properly | |
| 12 | 7-Aug-20 | MODINVOICE-182 | Thunderjet | https://folio-org.atlassian.net/browse/MODINVOICE-182 resolves a problem where fund encumbrances are not updated properly if the invoice line was created from an order line before opening the order Since both have financial implications, and finance/invoices are being used by several libraries in production now, we think it's best not to wait until the Honeysuckle release to fix these. Edited to add: both fixes are complete and ready for release Monday. | |
| 13 | 11-Aug-20 | UIDATIMP-617 | Folijet | Hi @hollyolepm @Mark Veksler @mdg @Harry One more Goldenrod hotfix, hopefully the last for Data Import. Missouri State identified a problem with matching on URLs (e.g. MARC 856 $u matching to Inventory Holdings eAccess URI field). See https://folio-org.atlassian.net/browse/UIDATIMP-617. There's no useable workaround. What say ye? | |
| 14 | 12-Aug-20 | UIDATIMP-508 | Folijet | Yesterday we released a hotfix for https://folio-org.atlassian.net/browse/UIDATIMP-596, to correct a schema inconsistency between UI and BE. We missed the fact that it has a dependency on the story https://folio-org.atlassian.net/browse/UIDATIMP-508, which is complete and on the main branch, but not on the Goldenrod branch. Without this fix, no field mapping profiles for holdings can be created or updated, so very critical. | |
| 15 | 12-Aug-20 | MODSOURCE-178 | Folijet | We also discovered a bug that has significant impact on Inventory. When a former MARC 001 field is moved to a MARC 035 identifier field, it does not display as a Resource identifier in the Instance. All is fine in the MARC record, but the identifier is not viewable or searchable in Inventory, and it cannot be used as a match in Data import match profiles. https://folio-org.atlassian.net/browse/MODSOURCE-178 | |
| 16 | 17-Aug-20 | MODDICORE-83 | Folijet | Hopefully the last hotfix for Data Import for Goldenrod. https://folio-org.atlassian.net/browse/MODDICORE-83 is a blocker for Lehigh and Simmons, which are going live this week. A library cannot update an instance and create a holdings via Data Import. This may be a regression, since we definitely have been able to add holdings and items to existing instances in the past. In any event, a significant problem, for which we're aiming to provide a hotfix this week. Seeking permission for this hotfix. Thanks in advance! | |
| 17 | 19-Aug-20 | MODUSERS-213 | Core: Functional | A new Q2 hotfix issue just appeared in Core Functional's backlog (it has bounced around between teams for a couple of weeks). I don't think it has been approved by this group yet: https://folio-org.atlassian.net/browse/MODUSERS-213 It's a TAMU-reported migration issue and will require quite a bit of back-end investigation (which means work Core Functional had planned for Q3 will need to be pushed to Q4). @Jason Root is going to see if he can repro it and provide more info. I wanted to share this here as a heads up and in case anyone had ideas for how this might be handled (e.g. should this be considered a hotfix release blocker etc). | |
| 18 | 19-Aug-20 | CIRCSTORE-226 | Core: Functional | RMB-684 "GET query returns no records when offset value >= estimated totalRecords" This affects all RMB based modules, and solves this P2 issue: CIRCSTORE-226 | |
| 19 | 19-Aug-20 | RMB-684 | Core: Platform | ||
| 20 | 19-Aug-20 | RMB-693 | Core: Platform | RMB-693 "Close prepared statements in PostgresClient stream get" This affects all RMB based modules, and solves this P1 issue: MODINVSTOR-540 "ERROR: prepared statement "XYZ" already exists" | |
| 21 | 19-Aug-20 | MODINVSTOR-540 | Core: Platform | ||
| 22 | 20-Aug-20 | MODINVSTOR-556 | Core: Platform | Please approve MODINVSTOR-556 + MODINVSTOR-557 for MODINVSTOR-559 v19.3.2 Q2 2020 Hotfix release. | |
| 23 | MODINVSTOR-557 | ||||
| 24 | MODINVSTOR-559 | ||||
| 25 | 21-Aug-20 | UIREQ-510 | Core: Functional | Seeking approval to include https://folio-org.atlassian.net/browse/UIREQ-510 and its twin https://folio-org.atlassian.net/browse/UICHKIN-193 in the Q2 2020 Hotfix release. | |
| 25 | UICHKIN-193 | Core: Functional | |||
| 27 | CIRCSTORE-233 | Core: Platform | Please approve mod-circulation-storage 12.0.3 (CIRCSTORE-233). This Q2 2020 hotfix upgrades RMB to 30.2.5 to fix CIRCSTORE-224 "Cannot save new Loan Policy", CIRCSTORE-225 "Cannot save updated Loan Policy", CIRCSTORE-226 "Missing records when offset >= totalRecords", CIRCSTORE-227 'Record "new" has no field "loanspolicy_fixedduedatescheduleid"'. | ||
| 28 | CIRCSTORE-224 | ||||
| 29 | CIRCSTORE-225 | ||||
| 30 | CIRCSTORE-226 | ||||
| 31 | CIRCSTORE-227 | ||||
| 32 | 27-Aug-20 | MODPATBLK-48 | Vega | I have two hotfixes for Q2 2020 Hot Fix #2. They are actually part of the ongoing battle to fix the issues with Automated Patron Blocks, which were mostly fixed by Q2 2020 Hot Fix #1. I believe these are the last two issues: MODPATBLK-48: Fee/fine limit not being enforced properly for automated patron blocks (the fee/fine block is not kicking in when it should be) MODPATBLK-51: I just realized this is only happening on SNAPSHOT, so I removed the RELEASE from this one. I only need approval for https://folio-org.atlassian.net/browse/MODPATBLK-48 | |
| 33 | MODCONF-59 | Core: Platform | RMB v30.2.6 contains 3 hot-fixes that make it more unlikely that RMB based modules become unavailable. There are 4 more modules that were upgraded to RMB 30.2.6, please approve for Goldenrod hot-fix 2 release: MODCONF-59 Release mod-configuration 5.4.2 MODPERMS-97 Release mod-permissions 5.11.3 MODLOGSAML-74 Release mod-login-saml v2.0.1 MODLOGIN-136 Release mod-login 7.0.1 | ||
| 34 | MODPERMS-97 | ||||
| 35 | MODLOGSAML-74 | ||||
| 36 | MODLOGIN-136 | ||||
| 37 | 28-Aug-20 | MODUIMP-24 | Core: Platform | RMB v30.2.6: MODUIMP-24 Release mod-user-import v3.2.1 | |
| 38 | MODINVOICE-193 | Thunderjet | I need approval for two Hotfixes that have been tested and are ready for deployment to bugfest. https://folio-org.atlassian.net/browse/MODINVOICE-193 This issues is causing the system to fail when trying to load an invoice and it's invoice line data | ||
| 39 | MODFIN-147 | https://folio-org.atlassian.net/browse/MODFIN-147 This issue was discovered by Lehigh and resulted in one of their budgets allocated value displaying incorrectly. It stems from users working on one record in multiple tabs at once | |||
| 40 | 02-Sep-20 | RMB-703 | Core: Platform | @cate @jakub @hollyolepm @Mark Veksler @mdg @Harry Please approve as Goldenrod hot-fix 2: RMB-703 "Full text search doesn't match URLs containing &" (released as RMB 30.2.7), MODINVSTOR-568 "Release mod-inventory-storage 19.3.3" (= upgrade to RMB 30.2.7), needed for MODDICORE-80 "Cannot match on eAccess URI field" to be released as MODDICORE-84 "Release v2.1.7". | |
| 41 | MODDICORE-80 | ||||
| 42 | 03-Sep-20 | UICHKOUT-644 | Core: Functional | we have a bug in Goldenrod which makes it impossible for proxy users to check out items to themselves. This has been noticed by @Brooks Travis and he thinks it could be a serious issue for MSU. Can this be approved for inclusion in the second hotfix release? https://folio-org.atlassian.net/browse/UICHKOUT-644 | |
| 43 | 04-Sep-20 | ERM-1090 | ERM | several sites have identified an issue in ERM in relation to linking documents to Agreements. It’s affecting/expected to affect at least 6 institutions and can cause issues when migrating from previous versions to Goldenrod. We have a fix and would like this be approved for a hotfix to Goldenrod please. https://folio-org.atlassian.net/browse/ERM-1090 | |