Skip to content
← All articles

Deliveries 10.1, 2025-02 and 2025-04, an optimized compatibility with GitLab

New delivery 10.1, 2025-02 & 2025-04

The deliveries of Squash (Squash TM 10.1 and Squash Orchestrator 2025-02/2025-04) contain the following features:

  • Improved management of requirement synchronization in Squash
  • Customization of Squash templates for GitLab Bugtracker
  • Customization of permissions in the Execution and Reporting workspaces
  • High-level requirements management in the API
  • Feature removals
  • Deprecated features

The full list of new features and bug fixes is available on Squash TM 10.1, Squash Orchestrator 2025-02 and Squash Orchestrator 2025-04.

Improved management of requirement synchronization in Squash

Synchronized requirement fields can no longer be modified directly in Squash, whether on the requirement consultation page, in milestone mode or by import. This is intended to facilitate the maintenance of your project requirements. In effect, the synchronized fields of a requirement will be updated the next time it is synchronized, overwriting any changes previously made in Squash.

When configuring synchronization, it is still possible to enable manual modification of the “status” field, in order to act on requirements that would otherwise no longer be updated.

Customization of Squash templates for GitLab Bugtracker

Configuring quick actions

To facilitate the use of quick actions (see definition) when declaring an issue, they can be configured to appear systematically in the issue declaration form for a given project. These quick actions will be executed by GitLab for each anomaly declared in this project.

Screenshot: GitLab Bugtracker plugin setup, Custom description template field containing the quick actions /assign me and /shrug

Customization of permissions in the Execution and Reporting Workspaces

Requires the Squash Ultimate offer.

We have continued to update the configuration of custom permissions in different Workspaces following the version 9 release. In version 10.1, it is now possible to configure permissions in the Execution and the Reporting Workspaces.

Screenshot: Administration - Profiles, configurable permissions of a profile for the Execution and Custom report workspaces

New permissions

To clarify and simplify the various permissions related to the Execution Workspace, a new permission called “Delete executions” has been added.

A new “Download” permission has also been added to the Reporting Workspace.

High-level requirements management in the API

Requires the Squash Premium offer.

Several API endpoints have been created to handle high-level requirements. The newly added endpoints are as follows:

  • POST Link
  • DELETE Unlink

Additionally, the API endpoint GET Requirement has been updated to integrate high-level requirements.

Feature removals

  • The JIRA Requirements plugin, which is no longer supported.
  • Support for PostgreSQL 13 and 14 has been discontinued.
  • Support for MariaDB 10.6 has been discontinued.
  • Squash TM 10.1 requires now Java 21.

Deprecated features

The following features are deprecated and will be permanently removed from Squash TM in the versions or on the dates indicated:

  • Squash TM 10.1: REST API authentication: basic mode will be disabled by default (token mode will be the default). However, configuration can be modified to use basic mode.
  • Squash TM 11.0, to be released in Q3 2025: Squash TM support of Allure reports will be dropped. Squash TM support of bugtracker RTC will be dropped. H2 DBMS will no longer be supported.
  • Squash TM 12.0, to be released in Q4 2025: The plugin for Jenkins will not be released anymore. Passwords hashed in SHA-1 will not work anymore.

For more information and further deprecations, please visit deprecation details.