It's all about the answers!

Ask a question

Is there a possibility to bulk move workitem between project areas with different processes?


Guido Schneider (3.4k1486115) | asked Jun 19 '17, 4:33 p.m.

Dear Jazz Users,

During our introduction of SAFe we got the question how to migrate from Scrum based project areas into SAFe based PA's without loosing information.

Exporting and importing, like suggested, is not an option. All links will not work. History will be lost, a lot of information must be redone be because the enumerations, planned for, categories etc. are not equal between the PAs.

So the question is, does there exist a workitem bulk mover, which allows to move selected workitems, to a new PA, and map the information like workitem type, severity, priority, planned for, filed against etc. during the operation.

I will answer this question by myself.
We faced this problem last year, but have not found any solution. So read my answer about what we have now implemented to solve this problem.

regards
Guido


Accepted answer


permanent link
Guido Schneider (3.4k1486115) | answered Jun 19 '17, 4:43 p.m.

Hi Jazz-Community,

are you aware of the new OpenSource 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 Workitem Mover, our Company has implementad as OSS project. You find it on https://github.com/jazz-community/rtc-workitem-bulk-mover-ui

This Bulk Workitem Mover allows you to move workitems between project areas on same CCM Instance. The Workitem 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.

regards
Guido S.
IBM Champion and Co-Founder DACH Jazz-Community



Ralph Schoon selected this answer as the correct answer

Your answer


Register or to post your answer.