GITHUB JIRA CLOUD
Sometimes, text could be formatted incorrectly when syncing GitHub issues and Jira Cloud issues. This could be caused by differences in GitHub Flavored Markdown and Jira Markdown.
You can prevent some text formatting errors during synchronization with Exalate scripts. The scripts convert GitHub Markdown and Jira Cloud Markdown into HTML during outgoing sync. In the incoming sync, HTML is converted into GitHub Flavored Markdown and into Jira Cloud Markdown.
This page is being revised as it is not accurate with the underlying tracker.
In this section
With this outgoing sync script, you convert the fields you send from GitHub Markdown into HTML. This HTML is later sent to Jira Cloud.
Converts issue fields from GitHub Flavored Markdown to HTML. You can replace
|Converts issue comments from GitHub Flavored Markdown to HTML|
This script converts HTML into GitHub Flavored Markdown.
This script works after you set up conversion from Markdown to HTML in Jira Cloud Outgoing sync.
|Converts issue fields from HTML into Markdown. You can enter the specific field instead of |
|Converts issue comments from HTML into GitHub Flavored Markdown|
This script converts Jira Cloud Markdown you send into HTML. This HTML will be sent to GitHub.
|Converts issue fields from Jira Cloud Markdown to HTML. You can enter an issue field you want to sync instead of|
|Converts comments from Markdown to HTML|
|Converts issue fields from HTML to Markdown. You can replace|
|Converts comments from HTML to Markdown|