When to use "internal value" in work item CSV expo
When should "internal value" be used during CSV export of work items? I am exporting work items from one RTC repository for import into another RTC repository, using 3.0.1 RC2.
http://jazz.net/library/article/69/ says "Note that the CSV Importer uses the display name of attribute values for the mapping. Ensure that you export display names and not internal values when using the CSV exporter from RTC."
In 3.0.1, to preserve multiple comments in a work item I have to export comments in internal format. (Feature 80489)
For best fidelity, which attributes should I export as internal values, and which as labels?
This is related to an earlier forum post, http://jazz.net/forums/viewtopic.php?p=56166#56166 , which drew no responses.
- Greg
http://jazz.net/library/article/69/ says "Note that the CSV Importer uses the display name of attribute values for the mapping. Ensure that you export display names and not internal values when using the CSV exporter from RTC."
In 3.0.1, to preserve multiple comments in a work item I have to export comments in internal format. (Feature 80489)
For best fidelity, which attributes should I export as internal values, and which as labels?
This is related to an earlier forum post, http://jazz.net/forums/viewtopic.php?p=56166#56166 , which drew no responses.
- Greg
One answer
Hi Greg,
this did probably not get answered because few people really tried it.
My best guess would be to use internal value only for the feature below. I would suggest to try on a test server. In general I would export only those ones where the external value does not meet my requirements.
I suppose internal values will not work if you have different process templates in the involved project. E.g. a literal enum.literal.1 in one project could be High:enum.literal.1 and in the second Low:enum.literal.1
The external value for elements e.g. for enumerations would in both cases have a High so the mapping would work better with the external value.
Thanks,
Ralph
this did probably not get answered because few people really tried it.
My best guess would be to use internal value only for the feature below. I would suggest to try on a test server. In general I would export only those ones where the external value does not meet my requirements.
I suppose internal values will not work if you have different process templates in the involved project. E.g. a literal enum.literal.1 in one project could be High:enum.literal.1 and in the second Low:enum.literal.1
The external value for elements e.g. for enumerations would in both cases have a High so the mapping would work better with the external value.
Thanks,
Ralph
When should "internal value" be used during CSV export of work items? I am exporting work items from one RTC repository for import into another RTC repository, using 3.0.1 RC2.
http://jazz.net/library/article/69/ says "Note that the CSV Importer uses the display name of attribute values for the mapping. Ensure that you export display names and not internal values when using the CSV exporter from RTC."
In 3.0.1, to preserve multiple comments in a work item I have to export comments in internal format. (Feature 80489)
For best fidelity, which attributes should I export as internal values, and which as labels?
This is related to an earlier forum post, http://jazz.net/forums/viewtopic.php?p=56166#56166 , which drew no responses.
- Greg