How to: Assign a Backlog Group to a different project in Agility

This feature is available in all editions


Why can't I assign a backlog group to a different project?


Backlog Groups cannot be moved down the project tree; they can only be moved up the project tree to expand the area of coverage. Moving them down the project tree contracts the area of coverage and risks losing items that might sit outside of the lower level project you select.

To introduce a backlog group/theme at a lower project level, you can:

  1. create a new backlog group/theme at the lower level in the project tree
  2. view the backlog and filter by the original backlog group/theme
  3. use the multi-select to select all backlog in the backlog group/theme and the Move to backlog group/theme option to move them all to the new backlog group

If there are closed items, you can choose to leave them in the old backlog group, or reopen to move them in the same manner as well. This might also require reopening closed iterations, depending on when they were delivered.

To do so, your project role must allow write access to the project to which you are trying to move the backlog group (or portfolio item). To move a backlog group, simply edit it, and then select a new project from the drop-down list.


Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.