XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: High
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Issue - View
    • Labels:

      Description

      Status Update

      Hi everyone,

      There are at least two related but distinct themes on this issue, so it's important that we address both of them to avoid any misunderstanding. The first is regarding tables and emoji in the new issue view. Due to technical constraints, some of you currently won't be able to create tables and emoji in the new issue view. This effects anyone who doesn't yet have the new issue view for full-page issues. We expect to remedy this over the next few months so that anyone using the new view will be able to create tables and emoji. The method for creating these, though, will be via markdown. For those of you in this category, if you need to create tables or use emoji in the meantime, you can click through to the old issue view or turn off the new issue view for now by going to your avatar > Personal settings.

      For anyone who already has the new issue view for full-page issues though, you can add tables and emoji to your content by clicking the table button in the UI, using the Shift + Option + T shortcut, or by pressing / (this is a handy shortcut to know) and starting to type "table". You can read more about markdown formatting in Jira Cloud in our documentation.

      The second theme is wiki markup generally. To be transparent, we are closing this issue as we have no plans to support wiki markup in the new editor and new issue view. We're supporting markdown across Jira, Confluence, and Bitbucket Cloud to provide a more modern and consistent editing experience. For anyone using multiple Atlassian products, we believe this will provide the best editing experience. You can read more about the changes here.

       

      Regards,
      Nehal Jain
      Jira Product Management

      Summary

      When attempting to create a table in the Comment or Description field in the New Jira Issue View, the table is not rendering correctly.

      Environment

      • Atlassian Cloud
      • New Jira Issue View

      Steps to Reproduce

      1. Ensure that you have enabled the New Jira Issue View
      2. Go to a board, click on an issue.
      3. In the Comment or Description field, attempt to create a table.
        • header
          text
      1. This also affects tags which are using the curly brackets.
        •  Text \{code}
           -- {noformat} Text \{noformat}
           -- {quote} Text \{quote}
          
          h3. Expected Results
           - In the field, you will see this table:
          ||header||
          |text|
          
           - The text in between the Wiki Markup tags will also be formatted.
          
          h3. Actual Results
           - The table will not rendered. Instead, you will see the literal characters without any formatting.
           - The text in between the Wiki Markup tags will not be formatted.
          
          h3. Notes
           - After attempting to create a table through the New Jira Issue View, editing the Comment or Description field from the Old Issue View, we can see that the Vertical Bar character (pipe symbol) is escaped.
          {code:java}
          \|\|header\|\|
          \|text\|
          
      • Similarly, all curly brackets will automatically be escaped.

      Workaround

      1. Disable the New Jira Issue View.
        • This can be done by Clicking on the Profile Icon at the bottom left -> Personal Settings (or Profile). Under the "Labs" section, disable the "New Jira Issue View".

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              msatriya Sadiq
              Votes:
              173 Vote for this issue
              Watchers:
              169 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: