Page tree

About these releases

19/20 October 2022
.

  • Authoring Platform 8.14.0: Release Notes
  • SCT Browser (TS Browser) 4.17.0: Release Notes
  • Reporting Platform 2.6.0: Release Notes
  • Release Management Service 1.15.0: Release Notes
  • This is a scheduled maintenance release for the Authoring Platform and related services. This release delivers Frequent Release Implementation (FRI) project enhancements and Reporting Platform (RP) refinements, together with AP maintenance, performance and stability enhancements, aligned with RMS release platform enhancements. AP 8.14.0 has 11 enhancements and 14 defect fixes. This AP deployment includes the TS Browser, so the SCT Browser 4.15.0 release notes are included here, but these are dated for the 19 October Public SCT Browser release, with 3 enhancements and 9 defect fixes. RP 2.6.0 has 2 enhancements with 1 new and 1 updated report, and 5 defect fixes. RMS 1.15.0 delivers 7 enhancements related to FRI process and validation refinements, and 1 defect fix.
    .
  • CRS 2.4.0: Release Notes
  • This is a scheduled maintenance release for the Content Request Service (CRS), to both the International CRS and US CRS, aligned to the AP 8.14.0 release, with 2 enhancements.

These are scheduled maintenance releases for the Authoring Platform (AP) coupled with the SNOMED CT Release Platform (RMS host) and the SCT Browser, all running on the Snowstorm Terminology Server with related services. These statistics also include scheduled maintenance updates to the International CRS and US CRS platforms.

This page presents aggregated statistics of all related changes, including related Release Management Service (RMS) validation rules and reports, Reporting Platform updates, and other AP support services together with the SCT Browser (AP TS Browser). 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

Analysis Number of tickets Proportion
Total
Getting issues...
100%
Content Team Reporter
Getting issues...
17%
Other Reporter, including Managed Service and External Authors
Getting issues...
18%
Test Team Reporter
Getting issues...
15%
Technical Team Reporter
Getting issues...
50%
Technical (performance/stability)
Getting issues...
15%

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
Loading...
Refresh

  • No labels