ReQonsult releases Version 2607 of the Polarion® Project Updater

(Berlin, July 23, 2026) Berlin, Germany – With Release 2607, ReQonsult GmbH is releasing Version 2.0 of the Polarion® Project Updater. The new version expands the solution from a tool for comparing and rolling out project templates to an end-to-end process for template management in Polarion® environments.

Going forward, companies can maintain their process models in a central template project, generate Polarion® project templates from them, deploy these templates in Polarion®, and distribute changes to existing projects in a controlled manner. This consolidates the previously separate steps into a single, traceable workflow. This reduces the effort required for manual exports and coordination and facilitates the consistent maintenance of larger project landscapes.

“With Version 2.0, we’ve come full circle – from a living process model to a scalable rollout,” explains Nick Entin, Head of Research & Development at ReQonsult. “Organizations can generate templates from any project, clearly resolve conflicts, and manage updates in a reproducible manner across many projects – including support for Polarion® 2606.”

A key new feature is the “Download as Template” function. From a template project configuration group, administrators can directly create a Polarion® project template in ZIP format. In doing so, they can specifically select the required Polarion® areas and exclude individual repository paths. The template.properties file required for the template is populated largely automatically.

In Version 2.0, configuration groups can be based on both uploaded project templates and an active template project. This allows you to manage the maintenance, versioning, and packaging of the process model from a single administrative view. The manual transition – previously required – between the maintained template project and the project template to be rolled out is significantly simplified.

Another key focus of this release is the handling of project-specific customizations. In the event of discrepancies between the template and the target project, responsible users can now clearly decide whether a local file should be retained, replaced with the template’s current version, or manually merged. Side-by-side comparisons, batch actions, and direct access from the Polarion® Repository Browser support editing even when dealing with a large number of conflicts.

For existing project landscapes, Release 2607 also offers an initial analysis of project-specific files. Known local customizations can be flagged before the first comparison and will subsequently not be unintentionally overwritten by template content. This facilitates the implementation of the Project Updater in environments where projects have been individually developed over an extended period of time.

Guido Majewski, Senior Consultant at ReQonsult and a key contributor to the conceptual development, explains: “Many customers have long been maintaining their process models in a template project – the bottleneck until now has been the controlled migration to templates and target projects. Release 2607 makes this very lifecycle manageable and reduces the risk of losing project-specific customizations.”

The technical foundation has also been expanded. The comparison engine now takes into account the most recently synchronized template status, the current target project, and the new template version in a three-way comparison. A semantic XML comparison filters out purely formatting differences, allowing the check to focus on content-relevant changes.

For larger project environments, synchronizations and rollouts for up to five projects can be initiated in parallel. An integrated HTML Help Center also provides administrators with searchable in-product documentation on configuration, comparison, conflict resolution, and rollout.

With Release 2607, the Polarion® Project Updater supports Polarion® versions 2506, 2512, and 2606. Existing configuration groups, project assignments, and rollout histories are preserved during the upgrade; manual data migration is not required.