Replies: 2 comments
-
You can use the Also, fields that are in the Source but that do not appear in the target are not migrated. You can filter the FieldToTag mapper by adding a
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks Martin for your answer.
Anyway, now people here made do with what they had and now there are no activities planned on this topic.
Thanks again anyway
Marco
From: Martin Hinshelwood nkdAgility.com ***@***.***>
Sent: giovedì 9 febbraio 2023 10:40
To: nkdAgility/azure-devops-migration-tools ***@***.***>
Cc: Solimano, Marco (DI SW DM TO&MOM DO ALM) ***@***.***>; Author ***@***.***>
Subject: Re: [nkdAgility/azure-devops-migration-tools] Filtering values for fields to be copied (Discussion #1101)
You can use the BlankFieldMap to remove the target field value.
Also, fields that are in the Source but that do not appear in the target are not migrated.
There is currently no way to have a filter on FieldToTag but as I am updating a fieldmap today I can add a regex filter that should give you what you want.
-
Reply to this email directly, view it on GitHub<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FnkdAgility%2Fazure-devops-migration-tools%2Fdiscussions%2F1101%23discussioncomment-4916777&data=05%7C01%7Cmarco.solimano%40siemens.com%7C680bbc449a1942c022e508db0a81a2f7%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638115324117377688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1GLPWzgi1vhX83epkcFXo%2F1P6e5Xh582U%2Bfyo%2FILPSE%3D&reserved=0>, or unsubscribe<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAU3CUQZ6IJCFACA7FUJFZHLWWS3PTANCNFSM5NSI5MHQ&data=05%7C01%7Cmarco.solimano%40siemens.com%7C680bbc449a1942c022e508db0a81a2f7%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638115324117377688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Vk6Y4WG4hcoOp%2FckhLvGFcJdaymCoBuacGl6zm45MM8%3D&reserved=0>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Good Morning,
is there any way to add some business logic to the migration tool?
Rationale:
We are migrating from TFS2018 to Azure DevOps and we are using your powerful tool to do that.
In Azure DevOps we're using a process template based on inheritance.
We have to overcome some limitations, for example: we don't want to maintain in the new template all fields defined in the old one. We decided then to write old field values in tag. Anyway, to avoid huge amount of useless tags (which causes a mess) we want to copy only significant values. Another issue is related to Value area allowable values: inherited process template permits only business and architectural. We've defined additional values that now are lost. We may save them in tags but, for the same reason, we want to save only values different from business or architectural.
At the end of the day, we might have something like:
Thanks in advance
Marco Solimano
Beta Was this translation helpful? Give feedback.
All reactions