Can I move or copy backlog items between projects?

Yes, you can copy backlog items between projects the same way as you can copy them within a project.

When you copy backlog items between projects, what you get are new backlog items with almost all, but not all, information and state copied from the original backlog items. The new backlog items will have new backlog item numbers and new ids, so they will be different backlog items from the original backlog items.

If you would like to move backlog items between projects, do a copy. Then, when you've double-checked that all information in the backlog items have been copied as you expected, either delete the original backlog items, or better, move them to a separate backlog list in that project to keep them around, until you're absolutely sure you don't need them anymore.

Tip: Instead of using multiple projects and copying between them, consider having multiple backlogs and backlog lists within the same project instead.

Here is what is copied when you copy backlog items between projects:

  • All of the basic information, such as name, description, type, and color
  • Estimates, status, and progress
  • Child backlog items inside epics (down to any level)
  • Tasks
  • Tags (if the same tags exist in the target project)
  • File attachments, comments, and checklists
  • Tracked time, including time entries
  • Contents of custom fields (if the same fields exist in the target project)

If you're using time tracking, note that the tracked time is copied too, including the time entries. Be careful that you don't count the same time twice, since the tracked time will then exist both in the source project and the target project.

Here is what is not copied when you copy backlog items between projects:

  • Backlog item numbers, backlog item ids, task numbers, and task ids
  • Assigned releases, sprints, teams, and Kanban boards
  • The specific board column that a backlog item or task is in, if this is a custom board column
  • Activity histories
  • Relationships
  • Commits in source control tools
  • External ids (as used in the Scrumwise API)

Also, mentions of backlog items, tasks, teams, etc. using the @-notation will continue to refer to the objects in the source project (so will not be changed to point to the corresponding objects in the target project).

When you copy backlog items between projects, and some persons have access to the target project but not the source project, those persons will be logged out of Scrumwise by the copy, and will have to log in again. This means they may lose work that have not yet been saved. If this will happen for a copy that you are about to make, you will be asked for confirmation before proceeding.

When you copy backlog items between projects, both projects must use the same units for estimates. If you would like to copy to a project that uses different units, here is what you can do:

  1. Create a new dummy project with the same units as the source project
  2. Copy the backlog items to the dummy project
  3. Change the units in the dummy project to match the target project
  4. Copy the backlog items from the dummy project to the target project
  5. Delete the dummy project (make sure it's the dummy project you delete!)

Still need help? Contact us Contact us