Moving Workitems from Project area A to Project area B

 Hello Vishnu,

Hi,

For our current project also we have this feature implemented. I am attaching the screen shot for your reference.

In our project we have this option for moving a particular work item into TRASH project area as delete option is not there.

For both the project areas we have a mandatory field -  Filed Against.

Having choosing the move option it will throw warning message saying "attribute not found" clicking OK will let you move to other project area.

In my experience the BulkMoveWorkItem tool didn't do what I needed programmatically.  I know Susan Hanson's team has done some work item migration work, but I went with a custom approach to what BulkMoveWorkItem does.

The key is the CopyToProjectAreaOperation class in the RTC SDK.  CopyToProjectAreaOperation.java is found in the com.ibm.team.workitem.rcp.rtc.feature.source_* plugin, com.ibm.team.workitem.rcp.ui_* subarchive, and the com/ibm/team/workitem/rcp/ui/internal/wizards directory.  This is enough of the brains behind moving a workitem between project, and can be adapted to even include changing workflows of work items.

Then I created a class that takes callbacks when a copy problem has been found, and modifies the work item's working copy accordingly.  For example, missing attributes, non-matching Filed-Against, that kind of thing.

For each work item in the list:

1. Disable all email to owner, creator, and subscribers
2. Create the working copy
3. Call CopyToProjectAreaOperation to get the list of copy problems
4. For each CopyProblem instance, attempt to resolve it
5. Run a final check on the working copy, because some attributes aren't set correctly, even without a CopyProblem
6. Save the working copy, looking for errors on save

With plenty of logging and tracking, it's pretty easy to do this gradually across multiple executions.  If you're going to disable email make sure to store the user's preferences beforehand, since some disable their mail notifications already, and you don't want to re-enable them incorrectly.

Susan's team's solution may be better, but this worked with the code that I've already written internally.

we found some odd behavior with the copy/move function in 4.0 as well. The current version 4.0.5 has vastly improved that function for us especially in the web which now has a straight copy operation for copy within the same project. We copy enumeration fields across projects regularly. Question about the fields enumeration in question. 1. are they enumeration or enumeration_list fields they behave differently. We do have enumeration fields that copy correctly. You have to ensure that the literal values are the same in both project area  process configuration source.If they are not you will run into the error you are receiving. Once we got the literals aligned we have no issues copy/move from project to project.