Page tree

About this release

25 November 2020

  • SCT Browser 3.16.0: Release Notes
  • MRCM Maintenance Tool 1.4.0: Release Notes
  • This is a scheduled maintenance release for the SCT Browser deployed as the Public SNOMED CT Browser. Changes include improvements to search query handling of pipe characters, display of flags in ECL results, display of language refset descriptions in the Refset panel, and three bug fixes (details in release notes). The Public MRCM Maintenance Tool was also updated to align with yesterday's AP release.

24 November 2020

  • Authoring Platform 7.2.0: Release Notes
  • Reporting Platform 1.14.0: Release Notes
  • MRCM Maintenance Tool 1.4.0: Release Notes
  • This is a scheduled maintenance release for the Authoring Platform (3 new features, including support for context specific language refsets, 8 improvements, 10 fixes), with associated updates for RVF validation assertions (1 new, 1 updated), an RVF performance optimisation, and aligned maintenance updates to both the Reporting Platform (2 new reports, 2 updated reports, 2 new report features, 7 improvements) and the MRCM Maintenance Tool (3 improvements).

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...
14%
Test Team Reporter
Getting issues...
12%
Technical Team Reporter
Getting issues...
55%
Technical (performance/stability)
Getting issues...
0%

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 T epic link
Loading...
Refresh

  • No labels