Skip to content

Conversation

@petersalomonsen
Copy link

The motivation for adding this feature was that work-items was already migrated without the iteration-paths being registered on the target, and also changed iteration-path names on the source after first migrations. In order not having to update all the work-items on the source, rather adding the option to update the target if the iteration-path is different.

@msftclas
Copy link

msftclas commented Nov 22, 2019

CLA assistant check
All CLA requirements met.

add config parameter update-work-items-with-different-iteration-path
which will update iteration-path on existing target work item if it's
different from the source iteration-path
@petersalomonsen petersalomonsen force-pushed the feature-link-iteration-path branch from a850a0c to 3fd8553 Compare November 22, 2019 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants