Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Description field in email notifications doesn't come through as HTML

I have set up an email notification using Automation for Jira that includes the Description field for issues. I am using the "htmlEncode" option for this field, but it still comes through with Jira wiki markup and no line breaks. The rest of the email uses HTML and looks fine. Any ideas?

2 answers

0 votes

Hi Janice,


This is now available. You can read up on it at -


Nick [Automation for Jira]

Hi Nick,

is this feature available in any server version? If yes, which Jira Software version and which Jira Automation version is required?

I could not quite figure this out looking at - it only shows a label "server-deployed".

My use case is using a web request to create a Confluence page, where I need the rendered XHTML content of the "description" field to be able to create the necessary XHTML storage representation for Confluence.

Best Regards

Robert Seeger

Jira / Confluence administrator at Germanedge

0 votes
John McKiernan Marketplace Partner Aug 20, 2019

Hi Janice, 

thanks for reaching out. John from Automation for Jira here. 

Your question comes at a good time. Until now, we have not been able to support this. However, as of yesterday, we have started working on a fix for this. You can track the progress here: 

I expect the improvement to be shipped within the next week or so. You shouldn't have any problems with it after that! 



Great! Thanks for the response. I'll keep an eye out for the update.

-- Janice

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events