Jira autmated Email lookupIssues.description.html not working to retain description format for email

[James_Gigantes]

Im trying to form an email report using {{LookupIssues}}

  

I get a result for lookup Issues and I can confirm that the description text is the same. Though I cant seem to pass the description text along with format (as html). It seems to come through as Wiki markup.

PROBLEM:   I am trying to pass *{{lookupIssues.get(0).description.html}}* in order to retain the format present in the issue when viewed on Jira cloud. Though when I place this in the email body, It retains the wiki markup and it wont convert to HTML. 

As an Automator, I would like my Issue format to carry through as HTML, so that Outlook can read the code and retain my formatting. 

[Mark Segall · Accepted solution]

Hi @James_Gigantes and welcome to the community!

I haven't tried this myself, but I believe it would be this:

{{lookupIssues.get(0).description.htmlEncode()}}

[James_Gigantes]

Sadly that didnt work. I also tried .html as I found on this LINK

[James_Gigantes]

I found that If I pass 

{{lookupIssues.get(0).description.text}}

 I can put the HTML in the description field and it passes through the automation and  renders properly

[Mark Segall]

Thanks for sharing the link.  According to the documentation, it's not foolproof.  

This may still not be appear as expected

When Jira sends HTML emails, it also incorporates all the styling into the email so therefore the HTML will look as it does in Jira.
Unfortunately, we don't have access to these styles so we just produce raw HTML with no styles.

If you're dealing with a repeatable structure, you may be able to deconstruct/reconstruct it.  For example, if the first line is always bolded, you could do something like this:

<strong>{{issue.description.text.match("^(.*)$")}}</strong>
<p>
{{issue.description.text.match("(?ms)(?!\A)^\S.*")}}

I know this isn't exactly what you're looking for, but it's an alternative option.

[James_Gigantes]

I have to master .match function. Thanks Mark! I will test this out. For the moment, it's good enough to pass. 

[James_Gigantes]

@Mark Segall Your suggestion pushed me to look a little harder at other solutions. I found that LookupIssues offers custom fields now. This is an awesome development. I will add some custom fields and create custom HTML formatting for each. Thanks!