--- title: "Tuleap 15.0 (sept. 2023)" slug: "tuleap-15-0" updated: 2026-01-23T14:28:49Z published: 2026-01-23T14:28:49Z canonical: "help.tuleap.com/tuleap-15-0" --- > ## 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.0 (sept. 2023) ## Farewell AgileDashboard and welcome to Backlog & Kanban It’s been cooking since the beginning of the summer and it’s there: AgileDashboard is gone to let the place to Backlog and Kanban services/tools. ![](https://www.tuleap.org/wp-content/uploads/2023/09/backlog-fs8.png)*New *Backlog* service landing page* ![](https://www.tuleap.org/wp-content/uploads/2023/09/kanban-fs8-2.png)*New *Kanban* service landing page* For new users (the main target of this change) it should be straightforward. However for long-time user, this might change some habits so we have released a [dedicated blog post to detail all the changes and the frequently asked questions](https://blog.tuleap.org/new-navigation-bar-splitting-the-agile-dashboard). ### Why did we do this change ? The Tuleap Service called AgileDashboard was misleading or could be misinterpreted. First, it was the only Service in Tuleap to actually cover two scopes. There was the Backlog scope and the Kanban scope. It mostly made sense back in time because it was all “Agile stuff” but in the end it was hard to grasp for newcomers. Second, the term AgileDashboard was a problem itself because of Agile and because of Dashboard (that start to make a strong case for its removal). Agile was a problem because it doesn’t qualify exactly what Agile it is (Scrum, Kanban, XP, SAFe, etc). And Dashboard was a problem because we already have other kinds of dashboards (Personal & Project dashboards). Finally, our user research showed that “AgileDashboard homepage” was little to not used at all. ### It’s only the beginning As shown in [the blog post video](https://blog.tuleap.org/new-navigation-bar-splitting-the-agile-dashboard), the side bar will evolve a lot in the next releases. Stay tuned ! ## Use markdown in Pull Requests The title should speak for itself. It’s now possible to use markdown everywhere in Pull Requests: - In the main comment (previously description) - In the file comments - In the overview - In the change view ![Preview of a pull request description formatted with markdown](https://www.tuleap.org/wp-content/uploads/2023/09/pr-md1.png)*Preview of a Pull Request description formatted with markdown* ![Usage of markdown during the review of files](https://www.tuleap.org/wp-content/uploads/2023/09/pr-md2.png)*Usage of markdown during the review of files* There is a convenient recall of the available syntax as well as a preview available prior to submit. ![Markdown syntax helper](https://www.tuleap.org/wp-content/uploads/2023/09/pr-md3-fs8.png)*Markdown syntax helper* This should help to build more elaborate (hence useful) comments in the review process. ## Removal of deprecated stuff This release is also the opportunity to clear some of the very, very old stuff: - [#34015](https://tuleap.net/plugins/tracker/?aid=34015&from_aid=32657) Drop support of management of system users and groups - [#33976](https://tuleap.net/plugins/tracker/?aid=33976&from_aid=32657) ForumML EOL - [#33995](https://tuleap.net/plugins/tracker/?aid=33995&from_aid=32657) Mailman EOL - [#33997](https://tuleap.net/plugins/tracker/?aid=33997&from_aid=32657) Drop support of CVS Age by itself is not the problem, it’s more what’s behind those pieces that was problematic. From a functional standpoint. It was time to let CVS go, almost anything (except maybe cp .bak and rcs) is better than CVS and the tooling itself starts to disappear (no longer shipped in RHEL9 for instance). Mailman (and mailing list) are now replaced by Enterprise Chat, plus it’s a nightmare to configure properly. And finally the management of users and groups (already off on new installations since 6+ years) are features from another time. This greatly improves the security of the system (less dependencies) and ease the burden of maintenance. ## Bugs and requests There were [41 bugs fixed and requests implemented](https://tuleap.net/frs/release/228/release-notes#!/linked-artifacts) during the 15.0 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 - [#34029](https://tuleap.net/plugins/tracker/?aid=34029&from_aid=32657) Remove HTML tags from translated strings in Title, Description and Initial effort semantics - [#34004](https://tuleap.net/plugins/tracker/?aid=34004&from_aid=32657) Field used in assignee semantic must be more visible - [#33999](https://tuleap.net/plugins/tracker/?aid=33999&from_aid=32657) in tracker printer version a js error is thrown - [#33994](https://tuleap.net/plugins/tracker/?aid=33994&from_aid=32657) Double linkification of references when “purifying” content in light mode ### Program management - [#33984](https://tuleap.net/plugins/tracker/?aid=33984&from_aid=32657) Program Timeframe semantic configuration must check datetime format - [#34033](https://tuleap.net/plugins/tracker/?aid=34033&from_aid=32657) Program service should be available even without DB entry ### Roadmap - [#33987](https://tuleap.net/plugins/tracker/?aid=33987&from_aid=32657) Roadmap widget does not fold/unfold correctly ### Git - [#34014](https://tuleap.net/plugins/tracker/?aid=34014&from_aid=32657) Git references are no more well extracted ### Import from Jira - [#34000](https://tuleap.net/plugins/tracker/?aid=34000&from_aid=32657) Jira mono-tracker shortname must be “issue” ### System & upgrade process - [#34021](https://tuleap.net/plugins/tracker/?aid=34021&from_aid=32657) ForgeUpgrage buckets might not be executed when they come from a not yet enabled plugin - [#34022](https://tuleap.net/plugins/tracker/?aid=34022&from_aid=32657) `tuleap config-set` should accept spaces in the value 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.