---
title: "Tuleap 15.7 (avr. 2024)"
slug: "tuleap-15-7"
updated: 2026-01-23T14:27:45Z
published: 2026-01-23T14:27:45Z
canonical: "help.tuleap.com/tuleap-15-7"
---

> ## 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 15.7 (avr. 2024)

## Quack your hands, Cross Tracker Search is back 🦆

First and foremost, we have resumed the work on Cross Tracker Search and it will be awesome. It will be the root of two major features of the year: SuperTableau and SuperKanban. We are going to blog on the roadmap soon, stay tuned !

Why searching across multiple trackers isn’t already there you might wonder.

Well, it’s not that simple actually.

One of the strength of Tuleap Trackers is their ability to be fully customized without platform privileges. The way you have to describe bugs doesn’t have to be the same than all other teams in the company. Similarly, it would make a lot of sense to have the same structure for capturing a user story for a team of three that just discovered Scrum and a team of twelve that does Scrum for years.

That’s all fun and games until someone wants to search over those different structures. How do I search if Team A decided that the title of their bugs is in a field called “Title” and Team B decided that it would be “Summary” ?

Actually, this one is already solved, we have “Semantics” for that (and in that case it’s Title semantic) and it’s already possible to run searches based on Semantics. However we cannot define semantics for everything, it would be tedious.

### If it walks like a duck and it quacks like a duck, then it must be a duck

That’s a concept [borrowed to Python programming language](https://en.wikipedia.org/wiki/Duck_typing). In our context it could be rephrased “if those fields have the same name and a compatible type, then it must be the same”.

Let’s go back to our two bug trackers, if both of them have a “Acknowledged date” field that is of type “date time”, we can reasonably assume that we can issue a search like `acknowledged_date >= NOW() - 1 week` to get what was acknowledged during the last week.

You got the bases of the concept, in details, what do we consider compatible types ?

- All numerics
- All lists with same bind type (eg a select box with static values and check box with static values) including open lists
- String and text fields
- Date
- Date time (to be clear: date and date time are [not compatible types](https://tuleap.net/plugins/tracker/?aid=10710#followup_144176))

![Cross tracker search result with a duck-typing search](https://www.tuleap.org/wp-content/uploads/2024/04/xts-fs8.png)

Cross tracker search result with a duck-typing search

The following steps for cross tracker search will be the ability to apply queries on group of trackers (for instance “all trackers of this project” or “all trackers from those project whose name is request”) and to select the columns to be displayed. Watch this space !

## More filters for pull requests

After introduction of the new pull request home page in the previous release, we added a few more filters:

- **Related to me:** shows Pull Requests where you are a reviewer or an author
- **Target branch:** shows Pull Requests where the selected branch is a target for the PR
- **Reviewer:** shows Pull Requests where the selected person is reviewer

![Pull request dashboard with all filters](https://www.tuleap.org/wp-content/uploads/2024/04/pullrequest-fs8.png)

*Pull request dashboard with all filters*

## Pull requests source repository

When a developer does a pull request from a fork, the source repository is now displayed in addition to the branch.

![Highlight of the source repository of a branch when doing pull requests from a fork.](https://www.tuleap.org/wp-content/uploads/2024/04/pr-src-fs8.png)

## Bugs and requests

There were [4](https://tuleap.net/frs/release/233/release-notes#!/linked-artifacts)[7 bugs fixed and requests implemented](https://tuleap.net/frs/release/235/release-notes#!/linked-artifacts) during the 15.7 release cycle. 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.

### Tracker

- [#37201](https://tuleap.net/plugins/tracker/?aid=37201&from_aid=35499) **Open values are lost during** **artifact** **move**
- [#37215](https://tuleap.net/plugins/tracker/?aid=37215&from_aid=35499) Jira tracker import is broken without enterprise plugin
- [#37184](https://tuleap.net/plugins/tracker/?aid=37184&from_aid=35499) User group binding ids can be confused with None value
- [#36834](https://tuleap.net/plugins/tracker/?aid=36834&from_aid=35499) Tracker_WorkflowUser must be able to see all artifacts

### Roadmap

- [#36845](https://tuleap.net/plugins/tracker/?aid=36845&from_aid=35499) **The Current Date Marker on the Road Map is off by 1 Month**

### Test Management

- [#36867](https://tuleap.net/plugins/tracker/?aid=36867&from_aid=35499) Test execution is not updated when using step buttons

### Kanban

- [#36805](https://tuleap.net/plugins/tracker/?aid=36805&from_aid=35499) **Kanban item not found when creating a card in Kanban**

### Backlog

- [#36886](https://tuleap.net/plugins/tracker/?aid=36886&from_aid=35499) Backlog is not only scrum

### Document

- [#37207](https://tuleap.net/plugins/tracker/?aid=37207&from_aid=35499) Cannot retrieve Document file versions if there are more than 100

### Git & Pull Requests

- [#37189](https://tuleap.net/plugins/tracker/?aid=37189&from_aid=35499) Wrong redirection to pull-request homepage

### Full text search

- [#37200](https://tuleap.net/plugins/tracker/?aid=37200&from_aid=35499) Fulltext indexation in error due to transaction

### Site & system administration

- [#37196](https://tuleap.net/plugins/tracker/?aid=37196&from_aid=35499) **Display OIDC providers used by a user in site administration user page**
- [#36858](https://tuleap.net/plugins/tracker/?aid=36858&from_aid=35499) Make sure existing SSHd host keys have the proper owner/permissions
- [#36885](https://tuleap.net/plugins/tracker/?aid=36885&from_aid=35499) Tuleap functions can be restricted per project
- [#36866](https://tuleap.net/plugins/tracker/?aid=36866&from_aid=35499) Site admin users are not expected to be able to checkout a SVN repository of a suspended project

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.

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.