docs/user-guide/backlogs-scrum/backlogs-faq/README.md
[!NOTE] With the release of OpenProject 17.3, the Backlogs module has undergone significant changes, including the introduction of redesigned sprint handling and updated functionality. As a result, this FAQ page has been revised to reflect the current behavior and concepts.
Please note that further improvements are already planned for OpenProject 17.4 and beyond. We will continue to update this page to keep it aligned with the latest product changes.
Before the OpenProject 17.3 release, the backlog module allowed defining versions that could be used in the left or right columns of the backlog module. There wasn't a designated column for the sprint, but rather the user could decide whether the version should be displayed in the left or right column.
All the versions that have been defined to appear in either the left or right columns are now migrated into a sprint. All the work packages associated with the version will also appear on the sprint.
We have chosen a view which is the same in all projects to maintain consistency. Each project you visit now shows backlog on the left-hand side and the sprints on the right-hand side. Usually the life-cycle of a work package starts in the backlog and then the work package moves to the sprint. This is why we decided to place the backlog as the first column and sprints as the second one.
First, you have to make sure the backlog module is active within a project.
All buckets have been migrated as sprints, which are now visible on the right-hand side. Starting with version 17.4, we are improving the possibility to add backlog buckets on the left-hand side, allowing you to sort and organize your backlog in a better way.
Your backlog automatically shows all work packages from your project which are not closed and can be worked on. With 17.4., it will be possible to exclude certain work package types from the automated backlog.
The backlog can be sorted manually:
You can use the automated sprint boards, which show the entire sprint scope.
Additionally, if you would like to see the parent/child relationships, please use the parent-child boards.
Nothing has changed with the Burndown chart. It is synced with the sprint object and can be accessed from the sprint bucket menu when a sprint is active.