---
title: "Tuleap 16.4 (fév. 2025)"
slug: "tuleap-16-4"
updated: 2026-01-23T14:22:57Z
published: 2026-01-23T14:22:57Z
canonical: "help.tuleap.com/tuleap-16-4"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.tuleap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tuleap 16.4 (fév. 2025)

## Reduce emails sent by Trackers

Tuleap can be chatty when it comes to Trackers. By default, as soon as you comment on or modify an artifact, you will get email notifications for all changes after that.

Starting 16.4, users can choose to disable this default behavior with two new preferences:

![Preferences utilisateurs pour les notifications dans les trackers Tuleap](https://www.tuleap.org/wp-content/uploads/2025/01/prefs-fs8.png)*User preferences for email notifications* 

By unchecking the two boxes, you will be notified when someone else modifies an artifact you created or you are assigned to. Of course this works together with the recently added “@user” notification. Even with those two boxes unchecked, you will still receive an email when someone pings you with “@username”.

## @user mention in pull requests

Everything is already in the title, the @user usage in Pull Request will trigger an email to the associated user.

![A pull request where someone used @alice to trigger an email to the associated user.](https://www.tuleap.org/wp-content/uploads/2025/01/pr-fs8.png)*Pull request author asked feedback to a user with @user ping* 

## Export Cross Tracker Search results to spreadsheet

Cross tracker search “default” mode is sun-setting and will be completely removed in the next release (16.5). We will migrate queries automatically but before doing that there was one feature that was still missing in “expert” mode: spreadsheet export.

![](https://www.tuleap.org/wp-content/uploads/2025/02/xts-xlsx2-fs8.png)*Export of a query as XLSX* 

## Bugs and requests

During the 16.4 release cycle, [30 requests were implemented](https://tuleap.net/frs/release/245/release-notes#!/linked-artifacts). Bugs and security fixes were already back-ported on Tuleap Enterprise builds. You will find below a detailed list of fixes. The most notable ones are in bold.

### Security

- [#41476](https://tuleap.net/plugins/tracker/?aid=41476&from_aid=39698) **Artifact permissions are not verified in the Cross Tracker Search widget – CVE-2025-24029 – Moderate**
- [#41434](https://tuleap.net/plugins/tracker/?aid=41434&from_aid=39698) **Initial effort field does not respect field permissions in the Taskboard REST card representation** – CVE-2025-22129 – Moderate

### Trackers

- [#41474](https://tuleap.net/plugins/tracker/?aid=41474&from_aid=39698) Colors associated with select box values are not displayed in the tracker report widgets
- [#41465](https://tuleap.net/plugins/tracker/?aid=41465&from_aid=39698) Expose a `submitter_user_groups` key in the artifact update webhook payload

### Git

- [#41445](https://tuleap.net/plugins/tracker/?aid=41445&from_aid=39698) **Import Git configuration variables in DB**
- [#40100](https://tuleap.net/plugins/tracker/?aid=40100&from_aid=39698) **Pull Request comment is empty after scrolling**
- [#41433](https://tuleap.net/plugins/tracker/?aid=41433&from_aid=39698) [Git] – Line number not aligned with code
- [#41459](https://tuleap.net/plugins/tracker/?aid=41459&from_aid=39698) Git: 2.46.1 -> 2.48.1
- [#41790](https://tuleap.net/plugins/tracker/?aid=41790&from_aid=39698) Allow to disable anonymous git web browsing
- [#41456](https://tuleap.net/plugins/tracker/?aid=41456&from_aid=39698) Add setting to make Git snapshots accessible only to authenticated users
- [#41430](https://tuleap.net/plugins/tracker/?aid=41430&from_aid=39698) Delete Git repository without shelling out to a system command

### Site administration

- [#41437](https://tuleap.net/plugins/tracker/?aid=41437&from_aid=39698) Fatal error on Available Plugins

  

Dans l'écosystème Tuleap, un artifact est l'unité de base pour suivre le travail. C'est un élément géré dans un "tracker", et englobe tout ce que vous pourriez traditionnellement appeler un "ticket", une "tâche", un "bug", une "exigence", etc.

Un Tracker est un outil de suivi d'un type d'information qui permet de créer, gérer et suivre un ensemble d'artifacts partageant une même nature.