Start, Scale and Succeed Agility webinar, September 17 👉Register
Start, Scale and Succeed Agility September 17 👉Register

Tuleap 10.8 December 2018


Cross tracker search (Tuleap Enterprise)

Example of cross tracker search export to CSV in LibreOffice

It’s now possible to get a full export in CSV of a cross tracker search queries with all the fields:

Fields that produce several values (multi select box, open lists, etc) are not exported as there is no good way to export them is CSV.

If you didn’t remember what Duck Typing is, it’s a jargon to describe an automated matching between difference sources. In our case the base problem we have to solve is that 2 trackers can be widely different (think a bug tracker and a requirement tracker) so a cross tracker search between them is like comparing apples to pears. However if you want to search across “issue”, “bug” and “request” trackers, it’s likely that you are going to find the same kind of information (eg. category, due date, etc). Duck Typing is this context means that if the 3 trackers have a select box field named “category”, it’s likely to represent the same thing so it’s considered the same information and displayed in one column (even if the actual values are different).

The duck-typing rule was a bit relaxed comparing the previous release: fields are “duck typed” if at least 2 trackers got the same filed/type (previously the field should have been in ALL trackers).

Warning: for list fields, the binding type (users, groups, static) is taken into account: if ‘category’ is a list of users in one tracker and a static list in another one, they are not “duck typed”.

Bug fixed and requests:


Introduce native Git Large File Storage support as a new Tuleap Community plugin.

Git LFS is a technology that offers a clean way to manage large binary files in git. Binaries are not well managed by “pure” git which was designed to deal with text only. Adding those binary files in git repo leads to huge repos that are very large and every developer has to clone them with the entire history (unless specified): more bandwidth is consumed, the server activity is higher because of large files and longer operations. Git LFS solves that by storing big files outside the git repository (but still versioned). Have a look at the documentation on how to get started with git lfs on your repository.

On Tuleap, gitlfs plugin must be installed and activated by site administrator and it’s then available automatically to all repositories. Projects only have to do the client side work et voila.

Warnings in Tuleap 10.8:

PHP 7.2

After a year long effort, Tuleap is now ready to be run on top PHP 7.2 engine. You are encouraged to switch to it ASAP to get the performance boost (some pages got 5 times faster).

How to switch:

Congratulation, you run PHP 7.2 !

Tracker Workflow administration (Under development)

The new admin interface is still under heavy development and is not usable at the moment. You can however have a look to the new UI by crafting the URL manually: /plugins/tracker/workflow/:tracker_id/transitions.

Document Manager

As part of the work on the new Document Manager UI 3 new REST routes were added. Those routes are:

In addition to that, the route GET /projects/{id} was modified to return a project documents entry point in additional_informations.


Prometheus instrumentation got a new metric:

Eclipse Mylyn connector

Mylyn connector 2.4 got released (comptabile with latest eclipse releases). It fixes a long standing bug where private projects were not listed (hence queries were not possible). Thanks to Vincent Hémery for his contribution.

Ansible playbooks

Several PRs were integrated in Tuleap Ansible Playbooks to make them compatible with latest Tuleap deployment constraints (nginx, fpm from remi, etc). Thanks to Aurélien Tisné for his contribution.


Releases stats

Bug fix





Timetracking (Tuleap Enterprise)

Test Management (Tuleap Enterprise)


Websites located at and other subdomains need to store and access cookies on your device. We need your acceptance. Get more information.

Yes, I agree No, I disagree