Replies: 6 comments
-
It seems that I have managed to fix this bug in this commit czechdude@46000f2 in TfsAttachmentEnricher.cs |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days |
Beta Was this translation helpful? Give feedback.
-
Can you submit a PR for this change? |
Beta Was this translation helpful? Give feedback.
-
Has the problem been solved ? I am running on version 12.0.36 and the problem still occurs. |
Beta Was this translation helpful? Give feedback.
-
We welcome additional PR's to support edge cases. The current solution requires that both the name + size combination is different. Can you show a screenshot of the files that you are wanting to migrate? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When using 11.7.7 with some type fixing, I managed to run the Work item migration (I can't run the latest 11.9.47, because the json with source/target endpoints just does not work) but noticed that the Attachments with the same name are not migrated.
I'm trying dev.azure.com from org A to org B migration.
attachment_exists.json.txt

attachment_exists_log.txt
I know it is an old version, but I haven't seen this bug reported yet, so I'm adding it.
Thanks!
Petr
Beta Was this translation helpful? Give feedback.
All reactions