Page tree

About these releases

  • 28 March 2024
    • SCT Browser (Public Browser) 6.2.0: Release Notes
    • This is a scheduled maintenance release for the Public SCT Browser, aligned to the Authoring Platform (AP) Version 10.2.0 release, with 2 enhancements and 3 defect fixes.
    • CRS 4.1.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 10.2.0 release, with 3 enhancements related to batch uploads and maintainability.
  • 27 March 2024
    • Authoring Platform 10.2.0: Release Notes
    • SCT Browser (TS Browser) 6.2.0: Release Notes
    • Release Automation Platform 4.2.0: Release Notes
    • Release Notes Management Service 3.2.0: Release Notes
    • Template Management Tool 2.1.0: Release Notes
    • This is a scheduled maintenance release for the Authoring Platform (AP) and related services. AP 10.2.0 has 24 enhancements and 10 defect fixes, including 13 enhancements and 2 fixes for the Reporting Platform. This AP deployment includes the TS Browser, so the SCT Browser 6.2.0 release notes are included here, but these are dated for the 28 March Public SCT Browser release, with 2 enhancements and 3 defect fixes. Release Automation Platform (RAP) 4.2.0 has 2 enhancements and 4 defect fixes. Release Notes Management Service (RNMS) 3.2.0 has 1 enhancement to add a preview screen to versioning. Template Management Tool (TMT) 2.1.0 has 1 enhancement to improve presentation of new semantic tags in the template filters.

These are scheduled maintenance releases for the Authoring Platform (AP), Release Automation Platform (RAP, formerly RMS), and SCT Browser, and related applications all running on the Snowstorm Terminology Server with related services, including an update to the Classification Service.

This page presents aggregated statistics of all related 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...
11%
Test Team Reporter
Getting issues...
10%
Technical Team Reporter
Getting issues...
60%
Technical (services/performance/stability/maintainability)
Getting issues...
25%

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