We are delighted to announce the long-awaited private preview of the new Markdown editor for the work item discussion. This exciting feature empowers you to utilize the Markdown syntax and editor for all future comments. The Markdown editor aligns with the same experience you encounter in other parts of the product, such as Pull Requests.
You have the option to keep your existing work item comments as they are or convert them individually to Markdown. Our migration process makes a best effort to convert the HTML to Markdown, and in the majority of cases, it works as expected. However, it’s important to note that the conversion may not always achieve 100% accuracy for large, complex comments that contain custom styles.
With the new Markdown editor, you can anticipate the following:
- Support for all of the essential Markdown formats. To explore further, you can learn more about Markdown.
- Smooth conversion of HTML tables or tables copied from emails into Markdown format. While we do a best effort conversion, please note that certain table formats may not achieve 100%.
- Use the
value
syntax for string highlighting. - Continued support for @mentions and !mentions.
New Boards Hub only
The Markdown editor is exclusively available through the New Boards Hub. It is important to note that certain scenarios may result in a less than ideal experience for users who are not enrolled in the New Boards Hub. For instance, if a comment is created in the New Boards Hub and a user opens that particular work item in the Old Boards Hub, the comment will display the Markdown syntax. If you are going to enroll in this preview, it is highly recommended that all users make use of the New Boards Hub.
Once you have enrolled in the preview, you cannot revert back to the old experience that uses HTML for comments.
It is important to note that this new Markdown editor for comments will replace the current HTML editor in the New Boards Hub. Once the feature is generally available, it will be the only editor for comments moving forward.
Enroll in the private preview
The intent of the private preview is to get customer feedback before the feature can be made generally available. If you are interested in enrolling in the private preview, please send us email and include your organization name (https://dev.azure.com/{organization}). Note that the preview is limited, and we will be capping the number of organizations who can participate.
We are excited to finally make this feature available and we hope you love it as much as we do.
0
I’m a little confused as to the impact of markdown in work items for those not participating. I tend to enable and use preview features long before anyone on my team does. Most of them are not yet even using the new board hub UI because of the concurrency update issues.
What I’m not clear on is the impact of using MD for those not participating. The blog mentions that you’ll see MD if you aren’t using the new UI and I’m fine with that. They are already used to seeing MD with wikis and whatnot. But if our organization is in the preview then does everyone starting using MD now or do we still need to flip the preview feature at the user level? Normally we allow users to enable preview features on their own and don’t mandate anything. I can see some users sticking with HTML (because they copy from documents and whatnot) so I don’t want to force everyone to use MD just because I want to preview the feature.