Azure DevOps

Azure DevOps support is fully integrated. The same template model from Jira applies, with a few extra controls for ADO-specific features like target field selection and editor format.

Work Item Types

Azure DevOps uses Work Item Types instead of Jira issue types. The defaults are User Story, Bug, Task, Epic, Feature, and Issue — but custom types are common in real instances.

In the template editor, when you set the platform to “Azure DevOps”, the Issue Type field becomes Work Item Type.

Target Field

Unlike Jira, Azure DevOps work items have multiple long-text fields, not just a single description. The template editor shows a Target Field dropdown with well-known fields:

• Description — the standard work item description.
• Repro Steps — only on Bug work items.
• Acceptance Criteria — User Story, Feature, Epic.
• System Info — system/environment information.

A common pattern: have a Bug template that targets Repro Steps, and a separate User Story template that targets Acceptance Criteria.

Custom fields

The dropdown also offers a Custom option. Select it and type the aria-label of any editor field on the work item form. The extension matches target fields by aria-label attribute, so any text field that ADO renders — including fields from custom process templates — can be targeted.

Tip: To find a field’s aria-label, right-click the editor in Azure DevOps, choose Inspect, and look at the aria-label attribute on the <div contenteditable> or <textarea> element.

Format

Each Azure DevOps template has a Format toggle that controls how the template content is stored and authored:

• Markdown (default for new ADO templates) — opens a dedicated Markdown editor in the options page with a formatting toolbar (bold, italic, headings, lists, code, links) and a live preview tab.
• HTML — uses the same rich text editor (TipTap) as Jira Cloud templates.

The format you choose in the options page does not have to match the editor type on the live Azure DevOps page. The extension converts automatically at injection time:

• Markdown template → RoosterJS editor: converted to HTML via markdownToHtml().
• HTML template → Markdown textarea: converted to Markdown via htmlToMarkdown().
• Matching formats: injected as-is.

This means you can author in whichever format you prefer — the content will look correct regardless of which editor ADO presents.

Dual editors on Azure DevOps

Azure DevOps pages can present two different editor types depending on project settings and field configuration:

1. RoosterJS — a Microsoft-maintained rich text (contenteditable) editor. This is the traditional default.
2. Markdown textarea — a plain <textarea> for GitHub-flavored Markdown, used when a project or field is configured for Markdown rendering.

The extension detects both editor types automatically and injects templates into whichever one is present. Quick-access buttons and dropdowns are placed into the appropriate toolbar (the RoosterJS command bar or the Markdown toolbar).

Project keys

Azure DevOps “projects” map cleanly to the extension’s projects field. Use the project name as it appears in the URL, e.g. MyTeamProject.

DOM contexts

Azure DevOps renders the same form in three different containers:

1. Full-page work item view — at /_workitems/edit/<id>
2. Side panel — most common during creation
3. Modal overlay — quick create

The extension’s adapter handles all three by selecting on aria-label attributes (e.g. aria-label="Description") instead of relying on container classes.

Known limitations

• Boards / sprint planning views aren’t supported — templates only appear on the work item form.