Page tree

About this release

27 July 2021

  • SCT Browser 4.4.0: Release Notes
  • Authoring Platform 8.3.0: Release Notes
  • This is a scheduled maintenance release for the Public SNOMED CT Browser, to add a new ECL Builder feature for easier entry of expression queries. The Authoring Platform (AP) TS Browser is also updated to match, hence the AP version change. The AP release notes are provided for consistency and version tracking but are identical to the SCT Browser release notes, since the only module changed is the TS Browser.

22 July 2021

  • SCT Browser 4.3.0: Release Notes
  • MRCM Maintenance Tool 1.8.0: Release Notes
  • This is a scheduled maintenance release for the SCT Browser deployed as the Public SNOMED CT Browser, with 7 improvements and 5 defect fixes, including a scrollbar fix for the SNOMED CT Release Statistics page. The Public MRCM Maintenance Tool was also updated to align with yesterday's AP release.

21 July 2021

  • Authoring Platform 8.2.0: Release Notes
  • Reporting Platform 1.18.0: Release Notes
  • MRCM Maintenance Tool 1.8.0: Release Notes
  • SCT Browser 4.3.0: Release Notes
  • Release Management Service (RMS) 1.0.0: Release Notes
  • This is a scheduled maintenance release for the Authoring Platform and related services. This release adds new features for the Frequent Release Implementation (FRI) project to introduce Service Acceptance Criteria (SAC) visibility into projects and tasks, providing a baseline for later elaboration and role-based access to task and project promotion workflow controls. For this release the features are not fully activated, so do not affect the existing task and project authoring flow, but are presented to allow familiarity to be gained prior to full role-based access and workflows in subsequent Authoring Platform releases. These features are key to our strategic requirements to support more frequent SNOMED CT releases. AP 8.2.0 has 23 new features and improvements (including 3 new and 3 updated templates, and 1 new Drools Rule), and 18 defect fixes. This AP deployment includes the TS Browser, so the SCT Browser 4.3.0 release notes are included here, but these are dated for the 22 July Public SCT Browser release, with 7 new features and improvements, and 5 defect fixes. Reporting Platform 1.18.0 includes 3 new and 7 updated reports, and MRCM Maintenance Tool 1.8.0 has 2 new features and 1 improvement. This is also the first scheduled maintenance release for the Release Management Service (RMS), as a new service grouping for the SNOMED Release Service (SRS), Release Dashboard (RD) and Release Validation Framework (RVF) application updates. RMS 1.0.0 corresponds to implementation of SRS auto-scaling to support more frequent releases of SNOMED CT, together with migration of the release platform hosting to Java 11 (for continued Java LTS version support).

These are scheduled maintenance releases for the International and Managed Service Authoring Platform, including Community Content support, running on the Snowstorm terminology server.

This page presents aggregated statistics of all related changes, including related Drools Rules, RVF validation report assertion, Classification Service updates, and Reporting Platform updates. It shows changes by type, functional area, and reporter, to give further insight into the nature and focus of this feature release, to which have been added the proportion of tickets raised by Content Team Authors, Testing Team and Technical Development Team, along with the proportion of Technical tickets related to performance and stability.

Fixes/Improvements/Features

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira


AnalysisNumber of ticketsProportion
Total
Getting issues...
100%
Content Team Reporter
Getting issues...
14%
Managed Service Reporter
Getting issues...
9%
Test Team Reporter
Getting issues...
23%
Technical Team Reporter
Getting issues...
54%
Technical (performance/stability)
Getting issues...
10%

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira


Fixes

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Improvements

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

New Features

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Managed Service

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Key Summary epic link
Loading...
Refresh

  • No labels