Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-69358

Sidebar / Modal WYSIWYG forms don't match Detail form

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • Editor
    • None
    • 0
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      The new cloud update introduced a new WYSIWYG form that does not support the same syntax as the old form, specifically related to {{{{preformatted-text}}}} and {{{{

      code blocks

      }}}}, but with other major inconsistencies as reported below. No clear documentation or link to said documentation can be found related to the new syntax, and the disparity between the two syntax schemes between the multiple forms.

      New Jira Cloud updates have introduced input form inconsistencies. Please depreciate the old forms & syntax, and standardize the "code snippets" used across ALL forms on Jira. Developers like to type in code, please let us do so.

      It would be beneficial to the community to do the same across connected platforms like Confluence as well. As of now, there are at least three different syntax systems in place between software packages on the same cloud platform.

      Expected

      All editors should work the same and handle the same syntax & styles.

      • sidebar issue description
      • sidebar comment
      • modal issue description
      • modal issue comment
      • detail view issue description
      • detail view issue comment

      Results

      The detail view forms support different syntax than the (new) sidebar and modal forms

      • {{{{preformatted text}}}} is not supported in new form, which uses the standard of {{`backtick`}}). if you enter {{{{text}}}} in the new form, it will escape all curly braces.
      • {{{{
        code blocks

        }}}} typed out get all of the curly braces escaped

      • new form seems to support the industry standard of {{```}} triple backtick to start a code block
      • new form formats the following text: {{text}} as italic, where the old forms (detail) format the exact same string as bold.
      • new form uses {{*text*}} to format bold (as you type) which has no equal in the older forms.
      • new form also allows the user to type {{text}} to get italic, which gives the user two ways to do the same thing, causing confusion.
      • new form has no way of looking at the "code" for the content, forcing the user into WYSIWYG mode; for developers (this tool is used for software development, right?) this is extremely annoying, and a major step backwards.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jloe joshloe (Inactive)
            Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: