Child pages
  • HTML and Jira Markup Conversion


Conversion between HTML and Jira Markup has been significantly improved starting from TFS4JIRA version 7.1. The main objective in version 7.1 is to convert most styles you could pick in TFS or Jira Rich Text Editors properly, and therefore some tags might not be covered if they are not listed at the default text editor.

HTML conversion works for description, comments and any RichText type fields.  Due to the complexity of HTML tree structure, parsing HTML and converting them to JIRA Markups might not be 100% accurate. You will find an example and a list of supported HTML tags below.


TFS/Azure DevOps (formerly VSTS)Jira

Supported Rich Text HTML tags




<i> / <em>_(tick)(tick)
<ul>- ITEM(tick)(tick)
<ol># ITEM(tick)(tick)
<h[1-6]> tagsh[0-6].(tick)n/a
<font color="*"> <span style="color: *">{color}(tick)n/a
anchor / mail link / external link


code panel{code}(tick)n/a
no formatting{noformat}(tick)n/a
<img> (internal images)!...!(warning)(warning)
<img> (external images)!..!(tick)(tick)

Known issues (Unsupported)

1) TFS4JIRA CLOUD - Native ONLY: At the moment, images in description or comments are not synchronized fully. TFS4JIRA keeps the <img> tag for the images, but it does not change its original href location.


If a user pastes an image in the description field, the description will be synchronized to the TFS work item with <img> tag having "href" attribute pointing to the Jira host. Therefore, users can see those images in the description field only if they have signed-in both the Jira instance and TFS instance at the browser.

2) Copied some customized HTML content and pasted it into the rich text editor might be converted unproperly during the synchronization.

3) Emoticons you use in Jira are also images. Because of the reason mentioned at the 1st point, TFS4JIRA converts them to some corresponding texts


JiraTFS / Azure DevOps (formerly VSTS)

  • No labels

This page has no comments.