Import/export work item across repositories
We have disconnected repositories that would like to collaborate on work. Our understanding is that import/export will update a work item if the import ID exists in the repository. So if both repositories have common ids for work, we could import/export between them (we can deal with the merge issue separately).
If we created one of the repositories as a repotools dump of an existing one, the work item IDs would match, correct? And we could push changes between repositories? This would work for the initial work item, but doesn't accommodate new ones. Is there a way to import a new work item and, if it doesn't exist, preserve the ID in the import CSV? Can we control ID values? Or for the import give an indication of what defines a "matching" work item other than id?
Are there any other ideas on how to share work items across repositories?
Many thanks.
If we created one of the repositories as a repotools dump of an existing one, the work item IDs would match, correct? And we could push changes between repositories? This would work for the initial work item, but doesn't accommodate new ones. Is there a way to import a new work item and, if it doesn't exist, preserve the ID in the import CSV? Can we control ID values? Or for the import give an indication of what defines a "matching" work item other than id?
Are there any other ideas on how to share work items across repositories?
Many thanks.
One answer
CSV import does not let you set a fixed Id for a work item, this is
provided during save automatically. However, using
value mapping you should be able to map a Id value to another value.
Though, if you take this path, you could as well
just edit the CSV file and correct the Id values to suit your needs.
More info is available in these articles:
- http://jazz.net/library/article/69
- http://jazz.net/library/article/522
If you have 2 repositories that want to collaborate, why not simply link
the 2 RTC project areas and use CALM links
between them (Related Change Request for instance).
Ben
On 17.12.2010 10:53, harryk wrote:
provided during save automatically. However, using
value mapping you should be able to map a Id value to another value.
Though, if you take this path, you could as well
just edit the CSV file and correct the Id values to suit your needs.
More info is available in these articles:
- http://jazz.net/library/article/69
- http://jazz.net/library/article/522
If you have 2 repositories that want to collaborate, why not simply link
the 2 RTC project areas and use CALM links
between them (Related Change Request for instance).
Ben
On 17.12.2010 10:53, harryk wrote:
We have disconnected repositories that would like to collaborate on
work. Our understanding is that import/export will update a work
item if the import ID exists in the repository. So if both
repositories have common ids for work, we could import/export between
them (we can deal with the merge issue separately).
If we created one of the repositories as a repotools dump of an
existing one, the work item IDs would match, correct? And we could
push changes between repositories? This would work for the initial
work item, but doesn't accommodate new ones. Is there a way to
import a new work item and, if it doesn't exist, preserve the ID in
the import CSV? Can we control ID values? Or for the import give an
indication of what defines a "matching" work item other than
id?
Are there any other ideas on how to share work items across
repositories?
Many thanks.