Unable to create new Jira issue with formatted description

  • 20 August 2021
  • 3 replies

Userlevel 1

I am creating a new Jira issue from an O365 email.  For the Description field I am using the Email body which has HTML Tags.  Here is my experience:



Pass HTML email body direct to the Jira Description All HTML markup is visible (very messy)
Use Text formatter to remove HTML Tags Looks great in Zapier, but in the Jira the new lines are removed.  Everything appears on one line!
User formatter to replace new lines with either \\ or \n, (trying both markdown and standard formatting values), Either \\ or \n is visible in the description, all on one line again!
Use Text formatter to convert the HTML to markdown The description is created with all Markdown visible.


It looks like Jira is trying to do some form of predictive formatting, as some email bodies (stripped of HTML) used to create the Jira description do show up with line breaks, but these breaks have big spaces (multiple empty lines added for every new line), which is almost as bad.  If I edit the description from within the Jira issue, just touching the text causes the whole field to collapse down to one line again.

Has anyone else encountered this and is there a workaround?  

3 replies

Userlevel 5
Badge +8

Hey @AshleyMorris!

I’ve been looking into this and it seems that the Jira Software Cloud integration is only able to send the descriptions across in plain text. As you’ve discovered, any HTML or Markdown formatting on Zapier's side is not rendered in Jira correctly. We have a couple existing feature requests for the ability to use HTML and Markdown formatting when creating new Jira issues so I’ve added your votes for those. 

I really wish I had a workaround to suggest here but it seems that there isn’t one at present. I can’t give an ETA on when either of those feature requests will be implemented but we will reach out to you by email as soon as they are! :)

Please add my vote and a vote for each person who work in my company too :D

Userlevel 3
Badge +3

Thanks for reaching out, @Manuel Puerto! I’ve added your vote and we’ll be sure to keep you and this thread updated as soon as we know more. While we can’t track your coworkers votes, hopefully you can keep them updated for us. 🙂