Rally to RTC migration restrictions
While trying Export/Import of Stories from Rally to RTC using .csv files, I noticed following limitations:
I am not using RTC Admin account... Is that be helpful to over come some of these limitations?
I understand that its .csv export/import so it must be having some limitations but the imported data doesn't seem to very helpful after loosing ids, parent-child relationships and other information.
|
Accepted answer
Ralph Schoon (63.3k●3●36●46)
| answered May 19 '15, 4:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please see An Overview of Project Fundamentals in Rational Team Concert 3.0 to understand the basic concepts of RTC.
1. See and also see Process Enactment Workshop for the Rational solution for Collaborative Lifecycle Management for how to customize RTC process and work items - take the version for RTC only. 2. You will need a custom attribute of type small string to maintain the Rally ID. RTC creates its own ID's and that can not be customized. 3. Owner mapping: You need the owner ID in RTC, otherwise the import of the value does not work. If you use LDAP, you can sync users in. If you have owners that no longer exist, you would have to create the user at least temporarily or remove the value. 4. Unclear what you mean, some values are created (Iterations), some you could add in the CSV file if they are defined in RTC. You could also change the process configuration to not require those attributes during import to manage setting the values later. 5. Change the operational behavior to not require these attributes. E.g. have a special role as primary role for the user that imports and disable the operational behavior for required attributes for work item save (server) and work item save (client). See Process behavior lookup in Rational Team Concert 2.0 and Process permissions lookup in Rational Team Concert 2.0 for how behavior and permissions work. 6. The importer can recreate relationships. See https://jazz.net/library/article/522 and https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.workitem.doc/topics/t_importing_work_items_csv_file.html . You basically have to add a column for the parent or child and provide the work item ID after a hash #. To be able to do this, the work item needs to be there and you might want to use the imported rally ID to recreate this relationship with the generated ID's. You need an account that has enough permissions in the project area - an admin there, with all permissions set. Note, even if the user is a project area administration user, if he does not have the permissions things won't happen. The administrator of a project area can however give his role the required permissions. You don't need to be a JazzAdmin to do this, but you need one that e.g. creates the users (e.g. using repotools and a CSV file). anoorva sinha selected this answer as the correct answer
Comments
anoorva sinha
commented May 27 '15, 3:53 a.m.
Thanks for a quick reply.
In Rally's exported .csv file, we have a column which contains the parent ids of stories. So exactly what I need to do. Could you please explore a little more? 1
You
anoorva sinha
commented Jun 11 '15, 3:43 a.m.
Hi Ralph, I have a confusion on point 4 and 5: What should be the Name of the new column created to store the parent link in RTC?
In RTC, this parent-child relationship in work item goes under Links tab ->Links->Parent. So how will it map this place once we re-import the data with new parent-link column?
1
If you export work items with parents, you can export the links as columns. I think the column is then called parent. Export from a test system and check.
anoorva sinha
commented Jun 11 '15, 7:33 a.m.
Thanks. It worked.
Thanks for sharing this!
showing 5 of 6
show 1 more comments
|
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.