Skip to content

Squash TM 10.X Release Notes

Upgrading the Java version

Starting from version 10.1.0, Squash TM is no longer compatible with Java versions lower than 21.

Required modification for MariaDB

Squash TM now uses sequences on MariaDB.
This change requires creating a role and assigning it to the database user. This must be done before upgrading to version 10.1.0.

To do this, run the following queries with a user who has full privileges: 

GRANT USAGE ON squashtm.* TO 'squash-tm'@'%' WITH GRANT OPTION;
CREATE ROLE alter_squash_table_seq;
GRANT alter_squash_table_seq TO 'squash-tm'@'%';
SET DEFAULT ROLE alter_squash_table_seq FOR 'squash-tm'@'%';
FLUSH PRIVILEGES;
squashtm should be replaced with the database name.
squash-tm should be replaced with the database username as defined by spring.datasource.username.

Changing the SAML plugin configuration

Version 10.1.0 makes important changes to the SAML plugin that require an update of the configuration, see Changes from version 10.1.0.

Changing the database access configuration

The port and the database connection are now configured via the Squash TM configuration file (conf/squash.tm.cfg.properties).

Modification of the database schema

The database schema has been modified, affecting tables related to test plans and execution test plans. If you currently extract data directly from the database, your scripts may need to be updated.
We strongly recommend using the REST API instead of direct database access for the following reasons:

  • Future releases will continue to include database schema modifications to improve Squash's performance and maintainability.
  • Direct database access will require ongoing script maintenance and updates on your side.
  • The REST API provides a stable interface that shields you from these changes.

If you need details about the schema changes for this version, you can contact the Squash Support Team.

First released version of Squash TM v10 series is 10.1.0

Due to a critical issue identified during final release testing, version 10.0.x was not released. Squash TM 10.1.0 is the initial release of the Squash TM 10 series.

Squash TM 10.2.8

Released on 10/17/2025

Corrections

  • Xsquash4Gitlab:
    • A GraphQL query complexity error was preventing the publication/update of notes.

Squash TM 10.2.7

Released on 09/22/2025

Corrections

  • Charts:

    • Some charts containing custom fields could not be displayed.

  • Jira Cloud

    • Xsquash4Jira:

      • 502 A remaining /search call was still used when reporting from Squash to Jira Cloud.
      • 501 Synchronization requiring multiple batches (whose size is defined by plugin.synchronisation.jira.batchSize) could terminate prematurely after the first batch.

    • Xsquash4Jira, Jira Bugtracker (Cloud) & Jira Automation Workflow:

      • 503 POST requests with /search/jql could fail in some cases.

  • Reports:

    • Creating certain execution progress reports required an excessively long execution time.

  • REST API:

    • The new squash.security.api-session.max-concurrent-sessions parameter introduced in 10.2.4 was not working correctly. It has been removed. A more robust solution will be introduced in a future version of Squash TM.

Squash TM 10.2.6

Released on 09/16/2025

Corrections

  • Xsquash4Jira, Jira Bugtracker (Cloud) & Jira Automation Workflow:
    • 495 Update SearchClient after Jira Cloud API /search endpoint removal

Squash TM 10.2.5

Released on 09/09/2025

Corrections

  • Xsquash4Jira & Jira Bugtracker (Cloud):
    • 482 Update following the deprecation of the Jira Cloud API /search endpoint.

Squash TM 10.2.4

Released on 09/05/2025

Evolutions

  • REST API:

    • A new squash.security.api-session.max-concurrent-sessions parameter allows limiting the number of simultaneous sessions that a given user can have with the REST API.
    • The login of the user making a REST API call is now recorded in the log file.
    • REST API calls referencing a non-existent id no longer generate stack traces in the log file.

  • GitLab Bugtracker:

    • "debug" level logs detailing the cache loading phases have been added to facilitate problem analysis during cache initialization.

Squash TM 10.2.3

Released on 09/03/2025

Corrections

  • Requirements:
    • For some large Squash TM instances, some requirement moves from one folder to another, whether done manually or performed during Jira/GitLab synchronization, could take a crippling amount of time.

Squash TM 10.2.2

Released on 08/18/2025

Corrections

  • Technical:
    • The tm-10.0.0-migrate-iteration-executions changeset included in the 10.0.0 upgrade script could cause the database update to fail.

Squash TM 10.2.1

Released on 07/21/2025

Corrections

  • SAML:
    • Authentication to the Squash API REST using Basic Authentication was not possible when the SAML plugin was enabled and configured.

Squash TM 10.2.0

Released on 07/03/2025

Evolutions

  • Xsquash4GitLab:
    • Continuity of synchronization comments in the event of GitLab token renewal (Project Access Token or other), when this involves a change of permissions and/or user.

Corrections

  • Bugzilla Bugtracker:

    • 459 The configuration of the plugin.bugtracker.bugzilla.cache-refresh.cron-expression property prevented Squash from starting.

  • Executions:

    • The display of an iteration's execution plan could be abnormally slow.
    • The button to launch a new execution, with or without a pop-up, could appear greyed out without any apparent reason.

Squash TM 10.1.0

Released on 06/03/2025

Evolutions

  • Requirements:

    • External requirements repositories are the source of truth for synchronized requirements.
      • Synchronized fields cannot be modified directly in Squash. These fields are updated with each synchronization.
      • A synchronized requirement cannot be converted to a high-level requirement.
      • A synchronized high-level requirement cannot be converted to a requirement.

  • Executions:

    • The tables of manual and synchronized sprint requirements can be filtered and sorted according to the values of the "Category", "Criticality" and "Status" columns.

  • Automation:

    • The livelog is removed and replaced by the final log file at the end of an automated suite execution.

  • Transverse / Ergonomy:

    • The breadcrumb trail and object paths are clickable and can be used to navigate through different spaces.
    • Updated help for configuring synchronized fields for Xsquash4GitLab and XSquash4Jira. Added an example of equivalence configuration in the expected format and a link to the official documentation.
    • The administrator is warned about the loss of visibility of currently linked issues when changing the Bugtracker associated with a project.
    • When modifying links between requirements, a pop-up prevents simultaneous editing of roles and codes.

  • Administration:

    • Permissions for Execution and Management spaces can be configured for custom profiles.
    • Added new permissions "Delete executions" in the execution space and "Download" in the management space.

  • Technical:

    • Upgraded to Java 21.
    • Upgraded to Spring Boot 3 and management of related deprecations.

  • Performance:

    • The performance of synchronizations executed through the Xsquash4Jira, Xsquash4Gitlab, and Redmine plugins has been improved.

  • GitLab Bugtracker:

    • GitLab "quick actions" can be inserted into the body of an issue when reporting it.
    • The project manager can customize the template with free text and/or a list of GitLab "quick actions" that will appear at the end of the "Description" section.

  • REST API:

    • Creation of API endpoints for high-level requirements management.
      • Creation, reading, modification of a high-level requirement.
      • Linking a simple requirement to a high-level requirement.
      • Removing the link between a requirement and a high-level requirement.

  • Authentication:

    • 327 The SAML plugin is compatible with ESAPI version 2.5.4.

Feature removals

  • The Jira Requirements plugin is permanently replaced by XSquash4Jira and is no longer distributed from Squash 10.1.0.
  • PostgreSQL 13, PostgreSQL 14, and MariaDB 10.6 are no longer supported.
  • Authentication to the REST API by "Basic auth" is disabled by default.

Corrections

  • Executions:

    • The display time of the error message for executing a test without test steps was variable. It is no longer possible to manually execute a test without test steps.
    • The issue reporting window was not displayed correctly if a project path entered in the project administration was incorrect.
    • It was impossible to delete a manual execution of a test that also had deleted automated executions.
    • It was impossible to delete a campaign if an automated execution had been interrupted.
    • The "% of successful steps" column of an execution plan was always valued at "0" when executing automated tests.
    • 360 The execution of tests to validate sprint requirements failed following the prior addition of an external attachment in the test cases.
    • 409 In execution mode, the scroll bar did not appear if the width of a table exceeded the size of the panel.

  • Reporting:

    • 324 The "contains all values" filter for charts was not taken into account correctly.

  • Automation:

    • Environment variables were duplicated for each ITPI.
    • The button to launch automated tests was not disabled for users with the "guest" profile.
    • 355 When opening an automated test tar report, a blank page sometimes appeared.
    • The "unstable" indicator was not activated if the failing assertions were not identical.
    • The column filters of automated suites were retained, even after hiding columns.

  • Import:

    • 123 The presence of spaces in the access paths to requirements and test cases caused the import to fail.
    • 280 Depending on the import file formats, when the numeric value 0 was entered as the only entry in a test step, the import failed.

  • Cross-functional:

    • Excessively long element names limited their identification in the association panels. Names can be truncated on the right or left.
    • Management of the error message when searching for an existing issue via a poorly formatted identifier.

  • Azure DevOps Bugtracker:

    • Added a cache system to display the issue reporting form more quickly.

  • Tuleap Bugtracker:

    • Non-editable fields were displayed in the "issue reporting" form.
    • 357 Test case information was not included in the "Original Submission" field.

  • Campaign and iteration report:

    • 447 Generation of the iteration report could fail when the [Include issue details] box was ticked.

  • REST API:

    • 235 The default sorting of GET requests was random.

Plugins

  • New version for all plugins: compatibility with Squash TM and fixes.
  • Plugin release notes are included in the Squash TM release note.

Compatibility with third-party softwares

Squash TM version 10.1.0 has been validated with the following versions of third-party softwares. It should be compatible with more recent versions.

Ticket management

Software Version
GitLab Cloud 17.9.0-pre
GitLab Server 17.6
Jira Cloud 10.01
Jira DataCenter 10.4.1

Anomaly management

Software Version
Azure DevOps Services 2025.01
Azure DevOps Server 2022.1
Bugzilla 5.0.6
Mantis 2.25.3
Redmine 6.0.2
RTC 6.0.3
Tuleap 14.4.99.130

Automating

Testing technologies Version
Agilitest 💎 2.3.0
Cucumber JVM 7.0.0
Cucumber JVM 4.2.6
Cypress 12.12.0
JUnit 5.3.2
JUnit 4.12
Katalon 💎 8.2.0
Playwright 1.43.1
Postman 8.12.1
Ranorex 💎 9.5
Robot Framework 6.1.1
SKF 1.14.0
SoapUI 5.6.0
UFT 💎 15.0.2