Tuleap

Start by collecting stories, bugs and tasks in a product backlog. A product owner can prioritize the list and drag selected items into a release or sprint. The Backlog guide also describes taskboard, burnup and burndown views for following the work once planning begins.

For flow-based work, a Kanban cardwall displays items from a tracker. A team can create a board for a tracker, choose visible card fields and filter the board with a public tracker report. The guide notes that filtered boards do not use Tuleap’s realtime feature.

Trackers can be set up separately for bugs, tasks, user stories, requirements or support requests. Fields such as status, priority, assignee and dates let the records match a team’s process. A configured workflow limits which state transitions users can make; the official guide notes exceptions for mass changes, copies and XML imports.

Tracker permissions control who can view, edit or approve records. Work items can be linked to related technical tasks or commits, giving a reviewer a path from a request or defect into the development record. Test role access and links with representative sample items before a wider rollout.

Requirements can be tracked through linked development and test work. Tuleap also offers project-linked documents and version history, which can keep specifications close to the issues they govern. Advanced document, baseline and cross-tracker behavior should be checked against the selected edition.

Development pages describe linking Git commits to bugs, specifications and releases, plus code review with line-level comments. Confirm the repository, CI and review connectors actually included in the chosen edition before replacing an existing development workflow.