Welcome to the Jazz Community Forum
Tranferring Work Items Between Projects
Is there a way to transfer Work Items between projects? We have several product lines that are built upon different core products. While the development cycle is different for the products we can routinely, mis-identify the product where an issue arises.
Take for example:
Product A is our base product. And it has its own Project (A)
Product B is a product that sits on top of Product A.And it has its own Project (B)
Products A & B are developed as two different Projects.
Product B is found to have an issue by QA who creates a Work Item.
A developer who works on Product B performs additional testing and identifies that the issue originates in Product A.
With the above being stated, is there a way to reassign the Work Item to a Category and Release outside the originating Project?
Take for example:
Product A is our base product. And it has its own Project (A)
Product B is a product that sits on top of Product A.And it has its own Project (B)
Products A & B are developed as two different Projects.
Product B is found to have an issue by QA who creates a Work Item.
A developer who works on Product B performs additional testing and identifies that the issue originates in Product A.
With the above being stated, is there a way to reassign the Work Item to a Category and Release outside the originating Project?
One answer
Hi
To move or copy single work items to a different Project Area, the work item explorer view provides a 'Move/Copy to Project Area...' context menu action. Be aware that the two Project Areas should base on the same process specification - otherwise moving is very difficult (think of workflows, enumerations or categories that do not match). Currently, the moved work item is opened in a work item editor, s.t. non-matching attributes can be corrected by hand.
Regards
Marcel
Jazz Work Item team
To move or copy single work items to a different Project Area, the work item explorer view provides a 'Move/Copy to Project Area...' context menu action. Be aware that the two Project Areas should base on the same process specification - otherwise moving is very difficult (think of workflows, enumerations or categories that do not match). Currently, the moved work item is opened in a work item editor, s.t. non-matching attributes can be corrected by hand.
Regards
Marcel
Jazz Work Item team