Teamforge should be able to move artifacts to another project when the target planning folder is defined.

Use case:
Moving a reported bug to an upstream project.

Environment: Teamforge 19.1

Scenarios:
- Same project
Source Planning Folder: MySourcePlanningFolder
Target planning folder: MyDestinationPlanningFolder
Paste in the Planning Folder View
Correct result: "Planning Folder set to MyDestinationPlanningFolder"

- different projects
Source Planning Folder: MySourcePlanningFolder
Target planning folder: (no value)
Paste in Tracker View
Correct result: "Planning Folder changed from MySourcePlanningFolder to None (no value)"

- different projects
Source Planning Folder: (no value)
Target planning folder: MyDestinationPlanningFolder
Paste in the Planning Folder View
Unexpected error: "One or more artifacts could not be assigned to the selected planning folder because their parent artifact is assigned to a planning folder in a different folder hierarchy."

- different projects
Source Planning Folder: MySourcePlanningFolder
Target planning folder: MyDestinationPlanningFolder
Paste in the Planning Folder View
Unexpected error: "One or more artifacts could not be assigned to the selected planning folder because their parent artifact is assigned to a planning folder in a different folder hierarchy."

These errors are incomprehensible because the target planning folder is clearly defined. It should be possible to perform the operation.
Is this behavior possibly a bug?

by: Holger H. | over a year ago | Trackers