How to remedy imported work items with Uninitialized state
We're using the bugzilla importer to get defects transferred to RTC. A
tweak to the work item workflow resulted in several work items being
imported with "Unitialized" state.
(1) Seems like there should be an option to abort the import if
something doesn't map well.
(2) Is there a way for us to remedy the WIs with uninitialized states?
Thanks, Brian
tweak to the work item workflow resulted in several work items being
imported with "Unitialized" state.
(1) Seems like there should be an option to abort the import if
something doesn't map well.
(2) Is there a way for us to remedy the WIs with uninitialized states?
Thanks, Brian
One answer
We're using the bugzilla importer to get defects transferred to RTC. A
tweak to the work item workflow resulted in several work items being
imported with "Unitialized" state.
(1) Seems like there should be an option to abort the import if
something doesn't map well.
(2) Is there a way for us to remedy the WIs with uninitialized states?
I have outlined a possible solution to this problem in
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/64722
HTH,
Patrick
Jazz Work Item Team
Comments
this is way old, but I am encountering on 3.0.1. extract from one project,
create a mapping file, for a different defect workflow, import workitems into project 2.
all the data comes over. all the workitems show 'uninitialized' in eclipse..
look ok in the web ui.
the only thing , the default resolution code is 'unresolved' in project 1 workflow, and 'fixed' in project 2 workflow. the export shows 'unresolved' even for workitems not in resolved state.
I am trying this approach
1) Depending on the amount of data imported and depending on whether your RTC repo is already in use, you could choose to correct the mapping file to take the unmapped state into account and re-import from bugzilla. This may not be an option for you
but I still get the same problem.
our states are not symmetrical between workitem types. how do I define the mapping file per type?
had to make a separate mapping file per unique workitem type.
(story, defect and all others)
and, if I allow the mapper to specify the exact planned for, in both source and target.. NONE of them are found..
if I take out the specific timeline and iteration names (path). works fine..