-
Bug
-
Resolution: Unresolved
-
Medium
-
Severity 3 - Minor
Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation
Steps to Reproduce
- Add a table to a field that supports markup, like the description field.
- Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to Convert wiki markup to HTML or plain text in Jira automation, for example:
{{triggerIssue.Description.html}} - Trigger the automation.
Expected Results
The email received contains a table that looks similar to what is in the description field of the Jira issue.
Actual Results
The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example:
Issue:
Email received:
Workaround
One workaround would be to use the below and it depends on email client.
{{issue.description.html.replace("<table class","<table border=1 class")}}
[AUTO-409] Tables do not get properly formatted when using the conversion to HTML in automation
| Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
| Description |
Original:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java} {{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround One workaround would be to use the below and it depends on email client. {code:java} {{issue.description.html.replace("<table class","<table border=1 class")}} {code} |
New:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java}{{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround One workaround would be to use the below and it depends on email client. {code:java} {{issue.description.html.replace("<table class","<table border=1 class")}} {code} |
| Description |
Original:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java} {{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java} {{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround One workaround would be to use the below and it depends on email client. {code:java} {{issue.description.html.replace("<table class","<table border=1 class")}} {code} |
| Component/s | Original: Action - Assets Objects (Create, Edit or lookup) [ 71693 ] | |
| Component/s | New: Action - Send Email [ 72798 ] |
| Labels | New: jsw-s13 |
| Component/s | Original: Automation [ 68402 ] | |
| Component/s | New: Action - Create, Edit or lookup Object [ 71693 ] | |
| Key | Original: JSWCLOUD-22944 | New: AUTO-409 |
| Support reference count | Original: 2 | |
| Project | Original: Jira Software Cloud [ 18511 ] | New: Automation for Cloud [ 22610 ] |
| Support reference count | Original: 1 | New: 2 |
| Description |
Original:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java} {{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Tables do not get properly formatted when using the conversion to HTML in automation h3. Steps to Reproduce # Add a table to a field that supports markup, like the description field. # Create an automation that sends an email, in the body of the email include the smart value for the text field, and convert it to HTML according to [Convert wiki markup to HTML or plain text in Jira automation|https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/], for example: {code:java} {{triggerIssue.Description.html}}{code} # Trigger the automation. h3. Expected Results The email received contains a table that looks similar to what is in the description field of the Jira issue. h3. Actual Results The table data is visible in the email received, but the table itself is not visible, so there is no shading in the header row, nor border in the table. Example: Issue: !image-2022-04-08-01-10-51-909.png|thumbnail! Email received: !image-2022-04-08-01-10-26-187.png|thumbnail! h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Support reference count | New: 1 |