Replies: 1 comment 1 reply
-
|
We do not use the REST API. We use the TFS Object Model. Its likley that all we need to do is enable the tool that fioxes the images to do so for markdown as well as html. Liley a Regex change. |
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.
-
With my migration I was surprised, that after successful tests some images missing in the comments.
I found out, that the images are missing using Markdown instead of HTML.
MS announce this recently: https://devblogs.microsoft.com/devops/markdown-support-arrives-for-work-items/
In our Azure DevOps I see newer comments with markdown, so there is a mixture oft HTML and Markdown. The migration creates only html based comments.
From the blog there is an information in the API about the format, but I did't find this. Maybe its related to the used object model.
Devopsmigration tool don't find the images (and don't copy the image), mentions (don't update usename) and the format is wrong as the destination is HTML.
There is an option for mentions descripted here: #2015
For a quick bad workaround for my running migration I convert the markdown to HTML (using Markdig). For the feature maybe there is the option to handle markdown, when this information is avaiable.
If some one missing an image, check if the comment is Markdown using e.g. using this link: e.g.
https://dev.azure.com/<ORG>/<ProjectID>/_apis/wit/workItems/<WorkItemID>/commentsThere is are format key that contains the information like e..g. markdown.
Beta Was this translation helpful? Give feedback.
All reactions