It is possible to create a backlog from scratch. However, due to the high number of parameters, it is recommended to use an existing template and adapt it.
Before you begin, make sure that the trackers and the Backlog service are installed and enabled in the project.
Important information
Depending on the project template chosen, you will have different levels of pre-configuration.
It is important to check which services are enabled or not in the project administration.
The default backlog configuration
When you first access the Backlog service, as the project administrator, Tuleap offers to 
.
A default template is automatically applied, inspired by agile methods. If you want to customize it so that it can be used in other cases (hybrid hardware/software, standards management, etc.), go to Create a Backlog from scratch.
Practical information
Depending on the template chosen to create your project, the Backlog may have already been created and pre-configured without any further action on your part.
Tuleap's Backlog tool is tracker-based. All the elements are therefore artifacts from several trackers.
By clicking on "Create a Backlog", several trackers have been created:
Bugs
Epics
Releases
Sprints
Tasks
User Stories
As well as two schedules:
Release Planning
Release Planning allows you to add Bugs and User Stories to a release.
This means that in the backlog, it will be possible to add Bugs and User Stories.
Sprint Planning
Hierarchy
A hierarchy of the different trackers created has also been set up.
This means that the backlog will contain releases, and the releases can then be composed of sprints.
Practical information
The hierarchy can be viewed in the administration of one of the project trackers.
Tailor the default configuration to your specific needs
It is possible to adapt the provided functional template to your business process by making some structural changes
Configure the Backlog from its administration
Scrum configuration options
In the Scrum configuration section, set the options for how the Backlog works.
Select the type of table you want to use:
the task board;
the Cardwall (old and not recommended).
You can also import a Scrum configuration from a file to apply to your Backlog, or export the existing configuration for reuse in another project.
From this page, it is also possible to add a Mattermost configuration and manage the different schedules.
Configuring the charts
You have the option to enable, or not, the option to display project burnup charts based on item progress, not effort progress.
Change the name of trackers
You have the option to change the names of the trackers if they don't suit you or you just want to translate them.
Add/Edit fields
Another simple adaptation is to add and/or modify fields in the trackers of the model in order to better describe the business.
To do this, simply go to the Tracker administration Tracker and make the necessary changes.
See the article on Tracker fields for more information on how to access them.
Important
Some fields should not be deleted or field names should not be changed. As a reminder, field names are technical names that are not displayed to the user. On the other hand, the label that is displayed to the user can be changed without any problem.
Here are the fields to pay attention to:
Remaining Effort: this field represents the remaining effort, it is used in the "User Story" tracker of our model. The field that you consider to represent the remaining effort must therefore be called "remaining_effort". However, you can change the label (the one that will be displayed in the forms) as you wish.
Capacity (used in the model's release and sprint trackers): The field representing capacity must have "capacity" as its name. However, you can change the label (the one that will be displayed in the forms) as you wish.
Change the semantics
Some elements of the tracker semantics are used for the proper use of Backlog:
"Done": This semantic is used for the calculation of burnup and velocity graphs.
Therefore, you must indicate which field value(s) (usually the status) represent an item that is considered complete."Timeframe": This semantic is used in sprints or releases for example.
"Cards": This semantic allows you to choose the values that are displayed on the Backlog cards.
The "Background color" part allows you to select a field whose value color will be the display color of the map.
"Estimated effort": The estimated effort is used in particular in the calculation of burndown.
Create a Backlog from scratch
To create a backlog without a template, create your own trackers first.
Then link them together from the Backlog administration by creating a new planning
Careful
Some field names must be respected to ensure that the features work properly.
Use the following technical names when creating fields:
remaining_effort: A field representing the remaining work, used primarily for User Stories and tasks.
impediment: a field indicating a blockage, displayed on the cards on the board;
start_date: A field representing the start date of a sprint.
capacity—A field representing the capacity of a sprint.
duration: a field representing the duration of a sprint;
Type: A field representing the type of a task, used to display the corresponding color on maps.
Failure to respect these names prevents certain information from being displayed or calculated correctly in the Backlog.