HI!
The table I added to the issue in Jira is stored in the {{issue.description}} field. I would like to create an automation rule that sends an email including this table. While the email currently contains both the table's text and HTML formatting, the result is not very readable.
Attached are screenshots showing how the table appears in Jira and how it looks in the email.
Is there any way to improve the styling of the email to make it more readable? It would be perfect when the table looks the same in the e-mail like in the issue.
kind regards,
Markus
Best would be what @Trudy Claspill suggests. The big advantage of this approach is that the email body will directly display the issue description, there is no need for your user to click once again.
Second best is to send the issue description exported to PDF. Although it is an extra click to open the PDF, it supports all formatting possible in the Description field and the resulted document looks professional:
See: How to send issue exports in PDF?
(Discl. this app is developed and supported by our team.)
Thanks for the suggestion regarding the PDF, but in this case I prefer to have the information directly in the body of the email.
regards,
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @markus_neuwald_canon_at
Disclaimer: I have not actually tested this out to see what works best. But here are some things to check.
Are you using the Send Email action or the Send Customized Email action?
In the former have you check the More Options to see what Send As is set to?
Alternately try the Send Customized Email action which has the additional Rich Text format for content.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill,
thanks for your suggestions.
The first (HTML) i already tried with the same result.
Today i tried the second ("customized email action") with RichText -> the same result.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found a partial solution in this post.
Using this smart value: {{issue.description.html}} and setting the email format to HTML formats the output as html, but did not include the table borders for my simple table:
issue view:
email content:
The post also talks about using .replace to make the borders show but doesn't provide the details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.