Page tree

About these releases

7/8 December 2022
.

  • Authoring Platform 8.15.0: Release Notes
  • SCT Browser (TS Browser) 4.18.0: Release Notes
  • Reporting Platform 2.7.0: Release Notes
  • Release Management Service 1.16.0: Release Notes
  • Classification Service 6.4.1: Release Notes
  • This is a scheduled maintenance release for the Authoring Platform and related services. This release delivers Frequent Release Implementation (FRI) project enhancements, Reporting Platform (RP) and Classification Service refinements, together with AP maintenance, performance and stability enhancements, aligned with RMS release platform enhancements. AP 8.15.0 has 18 enhancements and 12 defect fixes. This AP deployment includes the TS Browser, so the SCT Browser 4.18.0 release notes are included here, but these are dated for the 7 December Public SCT Browser release, with 6 enhancements and 4 defect fixes. RP 2.7.0 has 17 enhancements with 4 new and 5 updated reports, and 6 defect fixes. RMS 1.16.0 delivers 5 enhancements related to FRI process and validation refinements, and 3 defect fixes. Classification Service 6.4.1 is a patch release with 1 defect fix.
    .
  • CRS 2.5.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.15.0 release, with 1 enhancement and 2 defect fixes.

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

AnalysisNumber of ticketsProportion
Total
Getting issues...
100%
Content Team Reporter
Getting issues...
19%
Other Reporter, including Managed Service and External Authors
Getting issues...
8%
Test Team Reporter
Getting issues...
18%
Technical Team Reporter
Getting issues...
55%
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