---
title: "Tuleap 15.1 (oct. 2023)"
slug: "tuleap-15-1"
updated: 2026-01-23T14:28:40Z
published: 2026-01-23T14:28:40Z
canonical: "help.tuleap.com/tuleap-15-1"
---

> ## 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.1 (oct. 2023)

## Promoted Trackers & Kanban in Sidebar

Tuleap sidebar is one of the key components in the application navigation and it had one problem: it was too technical. The wording used in the sidebar was targeted toward people that were already used to Tuleap.

The best example is “Trackers”, if you are used to Tuleap you know what it is and you mostly know what you will find there. But if it’s your first landing, you have no clue of what this thing is.

With the ability to promote Trackers and Kanban, users will see terms of their own business instead of name of the tools.

Let’s take an example with “Issue Tracker” project template.

![A tuleap project with the sidebar highlighted on trackers & newly visible "Issues" tracker](https://www.tuleap.org/wp-content/uploads/2023/10/issue-tracking-fs8.png)*A project created from Issue Tracking template* 

The “Issues” term is now visible directly at project creation and, even better, when you hover the “Issues” name, there is a small + that directly points to new issue creation.

![Highlight of new arifact creation button in sidebar](https://www.tuleap.org/wp-content/uploads/2023/10/plus-issue-fs8.png)

The same principle applies for Kanban. Even if, most of the time, the Kanban term is more widely known than Tracker, it is still beneficial to have it in sidebar but for a different reason. In case of Kanban, the added value is to have, wherever you are in the project, access to most important actions in your project. In the following example, the project decided to promote their user story kanban to make it easily reachable.

![A Tuleap taskboard page with an highlight on new direct access to user stories kanban](https://www.tuleap.org/wp-content/uploads/2023/10/kanban-fs8.png)*Direct access to User Stories kanban from a release taskboard* 

Last but not least, with all those changes in the sidebar we decided to remove the possibility to collapse the sidebar. As we can now have sub elements (issues tracker, user stories or epics kanban, etc) that don’t have a known icon associated to them, a collapsed sidebar is more confusing as users won’t know where the are going to land on a click.

## Bugs and requests

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

- [#34340](https://tuleap.net/plugins/tracker/?aid=34340&from_aid=32658) Adding a “Last Modified by” criterion in report generates a PHP fatal error
- [#34380](https://tuleap.net/plugins/tracker/?aid=34380&from_aid=32658) Tracker reports can crash when searching on a bind list without any values
- [#34361](https://tuleap.net/plugins/tracker/?aid=34361&from_aid=32658) remove move artifact based on semantic
- [#33665](https://tuleap.net/plugins/tracker/?aid=33665&from_aid=32658) 0 in a a select box is presented as None
- [#34345](https://tuleap.net/plugins/tracker/?aid=34345&from_aid=32658) 0 value is discarded in int and float fields in the Artifact modal
- [#34338](https://tuleap.net/plugins/tracker/?aid=34338&from_aid=32658) Change from Markdown format to HTML is ignored in Artifact Modal

### Backlog

- [#34390](https://tuleap.net/plugins/tracker/?aid=34390&from_aid=32658) Create backlog should create backlog
- [#34370](https://tuleap.net/plugins/tracker/?aid=34370&from_aid=32658) Scrum is initialised even if administrator did not decide to
- [#34348](https://tuleap.net/plugins/tracker/?aid=34348&from_aid=32658) Add shortcut for backlog & kanban

### Kanban

- [#34369](https://tuleap.net/plugins/tracker/?aid=34369&from_aid=32658) Kanban widget fatal error during project creation

### Test management

- [#34016](https://tuleap.net/plugins/tracker/?aid=34016&from_aid=32658) Allow to order execution by definition rank
- [#34027](https://tuleap.net/plugins/tracker/?aid=34027&from_aid=32658) Artifact tooltip is missing in TTM

### Git & pull request

- [#34344](https://tuleap.net/plugins/tracker/?aid=34344&from_aid=32658) Git nested tags to unreferenced tag must directly retrieve initial commit SHA1
- [#34034](https://tuleap.net/plugins/tracker/?aid=34034&from_aid=32658) Interpret commonmark in pull-request comments notifications
- [#34706](https://tuleap.net/plugins/tracker/?aid=34706&from_aid=32658) Syntax highlight C++ files using the .cc and .hh extensions
- [#34708](https://tuleap.net/plugins/tracker/?aid=34708&from_aid=32658) Syntax hightlight Makefile files
- [#34396](https://tuleap.net/plugins/tracker/?aid=34396&from_aid=32658) Syntax highlight fo ipynb and rst files

### Document

- [#34397](https://tuleap.net/plugins/tracker/?aid=34397&from_aid=32658) Remove some unused views in document

### MediaWiki

- [#33985](https://tuleap.net/plugins/tracker/?aid=33985&from_aid=32658) No informations logged when LogUsersOutInstance get a 500

### Jira Import

- [#34349](https://tuleap.net/plugins/tracker/?aid=34349&from_aid=32658) Jira import must add assignee field in card semantic

### LDAP

- [#34381](https://tuleap.net/plugins/tracker/?aid=34381&from_aid=32658) Enable to get users when binding a directory group (contribution from Aurélien Tisné from CS-Group)

### API

- [#34389](https://tuleap.net/plugins/tracker/?aid=34389&from_aid=32658) Missing transaction when adding reverse links to created artifact
- [#34394](https://tuleap.net/plugins/tracker/?aid=34394&from_aid=32658) Cannot list trackers > 50 through API

  

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.