Why are work item approvals not getting imported?
I am doing a simple export / import of a single task with an approved review approval. In the exported csv file there is an Approvals field with a value of 'Review: Approved (1 of 1)'
Should this be getting imported to some part of the new work item? I checked the history tab and do not see it showing up there or Approvals or as a comment.
I am importing it back in to the same project area the work item was exported from, so there should not be any mismatch with the field name, and the new work item was created as a task as expected.
I see this article on how it can be done programmatically https://jazz.net/library/article/1118
and someone else asked about this a few years ago:
https://jazz.net/forum/questions/75812/import-work-item-approvals-from-csv
Thanks
Should this be getting imported to some part of the new work item? I checked the history tab and do not see it showing up there or Approvals or as a comment.
I am importing it back in to the same project area the work item was exported from, so there should not be any mismatch with the field name, and the new work item was created as a task as expected.
I see this article on how it can be done programmatically https://jazz.net/library/article/1118
and someone else asked about this a few years ago:
https://jazz.net/forum/questions/75812/import-work-item-approvals-from-csv
Thanks
Accepted answer
The CSV import does not support it as far as I can tell. Essentially the data format is not really good either. So you have to write your own importer. How to creat them can be found here: https://rsjazz.wordpress.com/2015/11/03/a-rtc-workitem-command-line-version-3-0/ and here https://rsjazz.wordpress.com/2012/10/01/adding-approvals-to-work-items-using-the-plain-java-client-libraries/ , https://jazz.net/library/article/1118 shows similar code. So feel free to create your own automation.
In the https://rsjazz.wordpress.com/2015/11/03/a-rtc-workitem-command-line-version-3-0/ I think I decided not to implement the import, because the parsing is a nightmare and setting the approval state won't work or be easy. A nightmare. Enough reasons not to do it.
In the https://rsjazz.wordpress.com/2015/11/03/a-rtc-workitem-command-line-version-3-0/ I think I decided not to implement the import, because the parsing is a nightmare and setting the approval state won't work or be easy. A nightmare. Enough reasons not to do it.
Comments
when we had to do this for our project copy utility we
imported the workitems, using the original ID as a new attribute column(old_id)
then searched on all the workitems where old_ID was not null,
then fixed up all the migrated workitems..
for the approvals we connected to both repos at the same time and copied the approvals over, cause as Ralph noted the data is hard to export
1 vote