For Tuleap 13.8 release, you’ll notice a lot of work was done for easier document management because it’s especially important for teams evolving in regulated environments. Also, for old pals of Tuleap, some updates on Baseline, and more!

Search for Documents

If you remember, two months ago, we disclosed in Tuleap 13.6 release note that we were working on a better search interface for Document. It’s now time for General Availability 🎉

So, what’s in there?

Search is accessible via the search input on the top right of your Tuleap interface. When using this input, you are searching for a match in all text properties and open the search interface. You can also decide to go straight to the search interface with the Advanced link (see screenshots down below).

Results of a search in Document
Results of a search in Document

By default, the search interface will propose all possible metadata as search criterion and all properties are rendered as columns.

Search interface configuration
Search interface configuration

Enforce naming conventions for Documents

When teams are working on regulatory documents (or any kind of formal documentation) they often face the need to have a general set of rules for document filenames. This is especially true when the documents are transmitted to a third party (auditor, customer, etc). In this situation, most of the time, it’s the file name of the document that is key to determining what we’re dealing with.

If it seems too abstract, to make it clear, we’re talking about files like doc12314_Project Orion_v1.0_final.pdf:

  • doc1234 refers to a unique number to identify your document in your quality management system
  • Project Orion refers to the actual title of your document
  • v1.0_final is a kind of tag that allows knowing, without access to the Documentation System, which version of the document you are referring to.

This is the kind of thing that Tuleap now allows enforcing via naming patterns.

NB: this is an opt-in, and customization is done, as usual, at project level.

Configuration of the pattern in Document administration
Configuration of the pattern in Document administration

Once the pattern is defined, the newly uploaded file documents will be automatically renamed according to the pattern. When using Documents, the creation of a new document or a new version dynamically displays a preview of the filename as it will be created (see screenshots down below).

Creation of a new document when pattern is defined
Creation of a new document when a pattern is defined

Then when creating a new version for the document, the version name can be used and the list of previously created versions is there as a reminder of the current state of the delivery.

Creation of a new version when pattern is defined
Creation of a new version when pattern is defined

General availability of Baseline

Baseline plugin has been showcased for the first time during TuleapCon 2019 (yeah, a long time ago). Back then, it was mainly a proof of concept to gather feedback. Now that we got feedback, it’s time to make it open for wider use.

NB: keep in mind that the feature set is still limited, it’s kind of “Series B” of feedback.

So for newcomers, what is Baseline?

Baseline allows taking snapshots of a set of artifacts at a particular moment in time. The artifacts can continue to evolve, but the snapshot remains untouched. It’s also possible to compare the snapshots to highlight what changed.

Create a baseline
Step 1: Create a baseline
Show the content of a baseline
Step 2: Show the content of a baseline

How is that useful?

The main use case is to be able to settle on something (an agreement, a contract) and let things evolve past this point. You can still refer to the agreement (the snapshot) while the underlying elements are living. If a problem arises, let’s say you’re late in your delivery, you can generate a proof of change (comparison of snapshots) to highlight that 70% of the requirements changed between the agreement and the review.

Test execution Document

Since Tuleap 13.4, it’s possible to generate a .docx document out of a Test Plan or a generic Test Campaign. This document contains the traceability matrix (requirements to test executions), the details of the backlog, tests, and tests executions.

However, until now, one piece of information was missing at test execution level: who did this and when. As it’s something that is often required by regulations, it’s now part of the generated document.

Test report with test runner details
Test report with test runner details

Docker images improvements

The documentation about Docker images usage was reorganized to make it clearer what are the configuration options at container initialization.

There are also two new options there:

  • Ability to inject site administrator email
  • Declare an extra Certification Authority (CA)

See the documentation for details.

Bugs and requests

There were 61 bugs fixed and requests implemented during the 13.8 release cycle. Bugs and security fixes were already back-ported on Tuleap Enterprise builds. You will find below a selection of the most notable fixes.



Site wide



Test Management



Receive once a month the latest Tuleap updates