Replies: 1 comment 1 reply
-
Yes. Its been on my backog for a while and I used to have a powershell that did this. I'm planning on a new command called "discovery" that wouldoutpost all of this info. But its a dream right now... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I migrated backlog of one of our projects from on-premise TFS to Azure DevOps. After migration, I noticed, that the source process was modified and some fields were added to work items. Because these fields did not exist in target work item, they were not migrated.
I would like to have som validation of work items, so the process notifies me if something is missing in target work item. I can then decide what to do with it. This feature should support.
Product backlog item
in source is mapped toUser story
in target, the check must be made between these two work item types.A
in source will be mapped to fieldB
in target. Then existence ofB
is checked in target. This may seem similar to whatFieldMappingTool
does. But in case of validation, no data are moved from source to target and this mapping is only for purposes of checking the existence of fields.I have already implemented it locally, because I need it. So my question is if it is something that could be incorporated in migration tool. If yes, I will make a pull request.
Beta Was this translation helpful? Give feedback.
All reactions