The Issues Full Table was not loading if a category has a single/multi select custom field with more than ~100k choices in it. From the UI it might appear that you only have 15k choices in it, but our database remembers all historic choices for reporting purposes. This causes some fields to have upwards of 1 or 2 million choices in the database. The full table is trying to render all 1 or 2 million, rather than filtering out the duplicate values.
If you were not already aware of this issue, then this does not impact you.
This is only impacting a few clients, but due to the critical nature of this problem to these clients we deployed a fix ASAP with no warning or announcement. We were able to deploy the fix without any downtime or impact to users.
This release is being managed through change control 301-40. You can download a copy of the first stages of the system release record, including the requirements and testing traceability matrix for release notes here: 2022.1P1 System Release Record 301-40 Release Notes. An entire release record will be available for review after the release is completed, in the auditor share account.
This release has already been deployed and there was 0 downtime.
ZenQMS comprises a microservice architecture that breaks up large functions into smaller services. This reduces risk in the development and release process. As such this flagship release version is actually composed of the releases of the individual services components. It is entirely possible for a component service to not change versions in a release cycle even if other components do. Here is the summary for this release.
ZenQMS Release 2022.1P1 contains the following “FixVersions”. We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.
- Change Control
- As noted above, deployment has already occurred
- There was no announcement for this release
- Deployment (as always) was handled by the ZenQMS team.