Tuleap 17.4 (Mar. 2026)

Tech preview: the future of Tracker

For several weeks, we have been working on harmonizing the display of application pages. This process is referred to as the Great Migration at Burning Parrot. This migration is not limited to a simple technical and aesthetic update: it also represents an opportunity to reassess the fundamental elements of Tuleap.

Today, we present the first phases of adjusting the reactor core: the setup of a Tracker's fields fields.

What are the adjustments, beyond the rendering?

Drag and drop

First of all, drag and drop! Fields can now be reorganized with the mouse, farewell to the infernal selection box "at the beginning of …" ;)

At this stage of the implementation, it is not yet possible to add new fields by drag and drop, but don’t worry, it’s coming very soon.

Centralization of field information

Fields can be linked to specific behaviors: semantics, workflow rules, etc. These elements are now visible in the fields interface and their configuration is accessible with a single click.

Towards a simpler and more consistent organization

The graphical organization of the different fields could be tedious and was not guided; we are proposing in this new interface a few simplifying rules to facilitate the construction of consistent interfaces. These rules are as follows:

• Field groups (fieldset) can only be placed at the root of a tracker

• A field can only be in a field group

• Columns are an organization of a field group. In other words, the admin can choose whether their field group has 1, 2, or 3 columns. They no longer directly manipulate the columns.

Important: trackers already in place will continue to work without any issue. The only restriction is that it will no longer be possible to create trackers that do not comply with the rules mentioned above in the future.

Migration to MySQL 8.4

The end of support for MySQL 8.0 is approaching (end of April 2026). The documentation has been updated as well as the default test suites to target MySQL 8.4 by default. We recommend planning as soon as possible your upgrade if not already done.

Bugs and requests

72 requests or bugs have been implemented during the 17.3 cycle, most have already been backported to the weekly Tuleap Enterprise Edition releases. Listed below are the changes outside the development process. Significant items are in bold.

Security

• request #47133 wasmtime: 36.0.2 -> 42.0.0

Trackers

• request #46803 Do not generate a random value when building list values

• request #46790 Artifact modal not aligned with artifact view on hidden list values

• request #46794 Improve index coverage for artifact links types

• request #46777 Image viewer crops oversized images

• request #46806 Artifact xml import may not import changeset

• request #46732 Open values de-duplication index can fail at update

• request #46760 Open values backup fails at update with numeric labels

• request #46748 Disallow burnup field in Trackers which are not in a planning

Cross-Tracker Search

• request #46762 widget_id is optional for API GET /api/crosstracker_query/content

Backlog

• request #46784 Create top backlog item representations only when needed

• request #46759 Wrong message in planning administration when using taskboard

• request #46376 504 Timeout error on milestone overview display

Document

• request #46769 Root folder should not expose an approval table

• request #47134 can no longer create new document from empty

• request #46778 Clicking on breadcrumb of current item can lead to a broken page

• request #27925 Document: when a new version of an image is uploaded the new image is not rerendreded in quicklook

• request #46770 Broken link on document

• request #27915 Document quicklook approval table not updated

• request #46385 Docman reactivity issues

• request #46394 In approval tables, link version are broken when they are not done on embbeded files

• request #46768 delete an emedded will raise an error

• request #46763 In document, item is not added to the correct position

• request #45606 Updated folder lost its content

• request #46752 Hint message when drag&dropping new files is broken

• request #45604 Error displayed when uploading a new version in Documents

• request #46751 Uploading a new file version always open the upload in progress modal

Git / Pull Requests / GitLab

• request #46772 Pull requests based on orphan branch cause internal error

• request #46812 Add missing index on the Git repository table to help fetching them

• request #46398 Links to GitLab repository broke after repository move

MediaWiki

• request #46780 Allow to install MW Standalone on a DB not supporting MyISAM engine

File release system

• request #46809 FRS Files not present in the UI

• request #46796 FRS packages are not recopied during the creation of a project from a template

Site administration

• request #46774 Missing title on site administration main page

• request #44855 OIDC connection failed because of too long username