Bulk Move Work Items between Project Areas in RTC plugin for 6?
Accepted answer
Comments
Yeah - I tried that and was told that it isn't supported by IBM. And that page has no contacts that I am allow to email (when I try, I get that I am not authorized to see their information). So, we are stuck with 1) wait FOREVER for IBM to decide that they did forget something important and decide to develop it; or 2) develop it ourselves. It was very useful to us and I didn't realize that it was not updated for v5. (I would have started telling everyone and their cousin before we went to v6 if I had realized, so I could try to stop the upgrade to v6 until the feature was available.)
2 other answers
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=91250
Hi Jazz-Community,
- 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.
Comments
In our organization, they promote RTC not GitHub. So I have no experience with anything GitHub. Also, we are not allowed to extend RTC at this time. We customize process templates only since that function is built into the tool, and prefer IBM's delivered solutions since our organization pays so much for IBM support. IBM's expectation that their paying customers also use open source solutions is a bit hypocritical. We could use a completely open source tool if we wanted to go that open source route. IBM seems to be making IBM obsolete.
Hi Donna,