Page tree

About this release

20 May 2021

  • Authoring Platform 8.1.0: Release Notes
  • Reporting Platform 1.17.0: Release Notes
  • MRCM Maintenance Tool 1.7.0: Release Notes
  • SCT Browser 4.2.0: Release Notes
  • Classification Service 6.0.0: Release Notes
  • This is a scheduled maintenance release for the Authoring Platform and related services, including platform migrations to Java 11 (new LTS version) for continued long term support maintainability. This release completes delivery of the Concrete Domains Implementation (CDI) project, providing full concrete domains features in the Authoring Platform to support authoring of SNOMED CT releases with concrete domains content following the July 2021 SNOMED CT International public release, and includes 27 improvements (including 1 new and 2 updated templates, and also 1 new and 7 updated validation Drools Rules) with 19 defect fixes plus Java 11 migration. Reporting Platform 1.17.0 includes 3 new reports, 6 report improvements and 2 defect fixes plus Java 11 migration, MRCM Maintenance Tool 1.7.0 (applied to both AP MRCMMT and the Public MRCMMT) has 2 improvements plus Java 11 migration. SCT Browser 4.2.0 (applied to both the AP TS Browser and the Public SCT Browser) has 6 improvements, 7 defect fixes (1 for the Release Statistics presentation) plus Java 11 migration. Classification Service 6.0.0 has 1 defect fix plus Java 11 migration.

This is a scheduled maintenance release for the International and Managed Service Authoring Platform, 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...
19%
Managed Service Reporter
Getting issues...
18%
Test Team Reporter
Getting issues...
14%
Technical Team Reporter
Getting issues...
49%
Technical (performance/stability)
Getting issues...
16%

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