2019.1 Patch 1 addresses two very narrow bugs linked directly to the new Change Control Module and its related components. The changes do not impact data integrity and have no impact on Stories/Requirements.
This release is being managed through change control 39175. Due to the possible impact on user data or configuration imports related to these issue we are treating it as a 'Critical' patch per the Quality Technical Agreement. As a result we will be releasing this patch as soon as QA completes testing protocols.
We do not expect any downtime.
AUTH-154 Mojo/auth sync failing when setting null/empty values for user's First/Last name
ZENQ-3699 Stage names repeated/duplicated if >40 stages are created in a category
You can download a copy of the 2019.1P1 Requirements & Traceability Matrix -- Summary Release Notes.
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 comprised 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 2019.1P1 contains the following “FixVersions”. We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.
CCM 1.0 - Change Control & Tasks Modules
AUTH 1.1 - Authorization service
PDF 1.0 - PDF generation service
Reports 1.0 - Reports Module
ZENQ 17.1 - Flagship application and all other modules/components that are not Change Control, Tasks or Reports