It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,863

question asked: Aug 07 '09, 8:01 a.m.
question was seen: 4,419 times
last updated: Jun 20 '17, 8:49 a.m.

Related questions

Bulk move of work items from one project area to another

0
Terrence Mystery (1●1●1) | asked Aug 07 '09, 8:01 a.m.
I had a project area that was created using the original scrum template. My server was upgraded to v2.0. Since there's no means of upgrading the existing template to the latest 2.0 version, I had a new project area created with the updated template. Now I want to move over the work items from old project area to the new project area. I found a web page (link below) that has some outdated plugins that enabled this functionality which don't seem to work with the GA level of the 2.0 client.

Can someone describe to me how I can accomplish the bulk move?


https://jazz.net/wiki/bin/view/Main/BulkMoveWorkItemsBetweenProjectAreas?rev=9

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Brian Wolfe (256●1●37●25) | answered Aug 07 '09, 2:20 p.m.
I've been looking for the same thing. Take note of the fact that all the attribute values need to line up in both projects for it to work without your having to save each work item individually. I did a bunch manually and it was quite a pain.
0
permanent link
Lukas Steiger (313●16●28) | answered Jun 20 '17, 8:49 a.m.

  Hi Jazz-Community, 


Are you aware of the new Open Source Jazz-Community on GitHub? The DACH Jazz-Community has founded this in May.2017. And we have now published some nice enhancements for RTC. 

Have a look at http://jazz-community.org 

One of the extensions is the WEB based RTC Bulk Work item Mover, our Company has implemented as OSS project. You find it on https://github.com/jazz-community/rtc-workitem-bulk-mover-ui 

This Bulk Work item Mover allows you to move work items between project areas on same CCM Instance. The Work item Mover is process aware and allows you to map types, enumerations etc. during the process. 
There are a couple of quite common use cases where moving selected number of Work Items is necessary:

  • Moving to another process template: There are multiple approaches to move to a new process template. One of it is to create an entirely new project area from scratch. Easily transferring the existing work items to the new area without changing the identifier and links is a key requirement there.
  • Splitting or merging projects: From our experience, changes in project structure or team setup often need to be reflected in RTC. As a result, project areas might be split or merged, raising the need to move the affected work items.
  • Defect Management: If, by example, your application is based on a platform, your users or customers may file defects against your application project area where they do not belong. You can then move them to the platform project area, whereas the issuer of the defect will still be able to receive updates on this defect.
See more on the GitHub project. Ideas, Enhancement Request, Defects can be filed directly there as Issues. If you like to collaborate on the development, please join us in the Community. 

Best Regards 
Guido Sschneider (IBM Champion and Co-Founder DACH Jazz-Community)
Lukas Steiger (Lead Developer and Co-Founder of github.com/jazz-community organization)

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.