"The Markdown editor was introduced in July 2025 to bring Markdown support to large text fields in work items. Since then, we've received valuable customer feedback highlighting challenges with the editing experience, particularly when switching in and out of edit mode."
"To address this, we've improved the usability of the Markdown editor by introducing a clearer distinction between preview and edit modes for large text fields. By default, fields now open in preview mode, allowing you to comfortably read and interact with content without accidentally entering edit mode."
"This change reflects how most users interact with Markdown editors. By reducing accidental edits and making interactions more intentional, the experience becomes more predictable, less disruptive, and overall more intuitive."
"We've already been rolling this improvement out to a subset of customers to gather early feedback. So far, the response has been positive. Based on that feedback, we're now expanding the rollout to all customers over the next two to three weeks."
The Markdown editor was introduced in July 2025 to support large text fields in work items. Customer feedback indicated confusion and disruption when switching between edit and preview modes. To improve usability, a clearer distinction has been made, with fields now defaulting to preview mode. Users can enter edit mode by clicking an icon, reducing accidental edits. This change aligns with user interaction patterns, making the experience more predictable and intuitive. The rollout is expanding to all customers after positive initial feedback.
Read at Azure DevOps Blog
Unable to calculate read time
Collection
[
|
...
]