Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-409

Tables do not get properly formatted when using the conversion to HTML in automation

    • Severity 3 - Minor

      Issue Summary

      Tables do not get properly formatted when using the conversion to HTML in automation

      Steps to Reproduce

      1. Add a table to a field that supports markup, like the description field.
      2. 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}}
      3. 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

            Kevin Sanghvi added a comment - https://getsupport.atlassian.com/browse/PCS-241964

            Milan Ardeshana added a comment - - edited

            following workaround works fine for my case :

            {{issue.description.html.replace("<table class","<table border=1 class")}}
            

            Milan Ardeshana added a comment - - edited following workaround works fine for my case : {{issue.description.html.replace( "<table class" , "<table border=1 class" )}}

            +1

            Suggested workaround only removes additional line breaks, but as original table. We still need full solution.

            Infinidat Jira Admin added a comment - Suggested workaround only removes additional line breaks, but as original table. We still need full solution.

            I was able to workaround this issue by unchecking "Convert line breaks to HTML line breaks" listed under "More Options."

            Unchecking this option resulted in the expected email formatting. 

            Joel Coates added a comment - I was able to workaround this issue by unchecking "Convert line breaks to HTML line breaks" listed under "More Options." Unchecking this option resulted in the expected email formatting. 

            It would be good to release a report on this when this is fixed as this is a confusing approach (instead what if we added a .markUp making the output for .html to occur by default when emailing. Outlook and Gmail are 2 of the largest email services, they both convert HTML to visual elements.  I have yet to realize any email handlers that will process tables  or other formatting as it is processed in Jira. 

            James.Gigantes added a comment - It would be good to release a report on this when this is fixed as this is a confusing approach (instead what if we added a .markUp making the output for .html to occur by default when emailing. Outlook and Gmail are 2 of the largest email services, they both convert HTML to visual elements.  I have yet to realize any email handlers that will process tables  or other formatting as it is processed in Jira. 

            Please get this to work. I cant form reporting emails with this janky markup language. This would save hours of time, confusion, and promote alignment. I would expect when attaching issue.description to an email would ideally work without the .html option. I have found many requests online for such behavior. I would have to utilize regex otherwise.  

            James.Gigantes added a comment - Please get this to work. I cant form reporting emails with this janky markup language. This would save hours of time, confusion, and promote alignment. I would expect when attaching issue.description to an email would ideally work without the .html option. I have found many requests online for such behavior. I would have to utilize regex otherwise.  

              Unassigned Unassigned
              rchiquete Rene C. [Atlassian Support]
              Affected customers:
              24 This affects my team
              Watchers:
              30 Start watching this issue

                Created:
                Updated: