{"id":72608,"date":"2026-04-01T09:17:11","date_gmt":"2026-04-01T17:17:11","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=72608"},"modified":"2026-04-01T09:17:11","modified_gmt":"2026-04-01T17:17:11","slug":"improving-the-markdown-editor-for-work-items","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/improving-the-markdown-editor-for-work-items\/","title":{"rendered":"Improving the Markdown Editor for Work Items"},"content":{"rendered":"

We introduced the Markdown editor in July 2025 to bring Markdown support to large text fields in work items. Since then, we\u2019ve received valuable customer feedback<\/a> highlighting challenges with the editing experience, particularly when switching in and out of edit mode.<\/p>\n

Many users found the current interaction model confusing and, at times, disruptive. For example, entering edit mode through actions like double clicking could feel unexpected and interrupt the flow when simply trying to read or review content.<\/p>\n

What\u2019s changing<\/h2>\n

To address this, we\u2019ve improved the usability of the Markdown editor by introducing a clearer distinction between preview and edit modes for large text fields.<\/p>\n

By default, fields now open in preview mode, allowing you to comfortably read and interact with content without accidentally entering edit mode. When you\u2019re ready to make changes, you can explicitly click the edit icon at the top of the field to switch into editing.<\/p>\n

\"markdown<\/a><\/p>\n

Once your updates are complete, you can easily exit edit mode and return to preview mode.<\/p>\n

\"markdown<\/a><\/p>\n

Why this matters<\/h2>\n

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.<\/p>\n

Rollout plan<\/h2>\n

We\u2019ve 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\u2019re now expanding the rollout to all customers over the next two to three weeks.<\/p>\n","protected":false},"excerpt":{"rendered":"

We introduced the Markdown editor in July 2025 to bring Markdown support to large text fields in work items. Since then, we\u2019ve received valuable customer feedback highlighting challenges with the editing experience, particularly when switching in and out of edit mode. Many users found the current interaction model confusing and, at times, disruptive. For example, […]<\/p>\n","protected":false},"author":921,"featured_media":66588,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[224],"tags":[7263,7314,7262,7316,7321],"class_list":["post-72608","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","tag-devops","tag-azure-boards","tag-azure-devops","tag-community","tag-markdown"],"acf":[],"blog_post_summary":"

We introduced the Markdown editor in July 2025 to bring Markdown support to large text fields in work items. Since then, we\u2019ve received valuable customer feedback highlighting challenges with the editing experience, particularly when switching in and out of edit mode. Many users found the current interaction model confusing and, at times, disruptive. For example, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72608","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/921"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=72608"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72608\/revisions"}],"predecessor-version":[{"id":72613,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/72608\/revisions\/72613"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/66588"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=72608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=72608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=72608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}