Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8175

WIKI markup doesn't let me over-ride text formatting.

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description


      I was simply typing a comment in an issue (JRA-8165) that had some characters like underscores or plus signs, as one might do when describing an issue. Unbeknownst to me, these are text effect "tags" in the new wiki markup scheme. That just won't do. If I explain that an error occurs when a user types in

      "_xxx_"

      , I want to see the actual underscores in the issue description, not an italicized version of what's in between them: "xxx". HTML tags work because
      1) the tags/codes are not likely to be used in the normal course of typing
      2) they are ways to escape them if necessary, but only a programmer would ever need to know how to to that
      In what is being presented here within JIRA, a casual user would not likely try to figure out how to get around the automatic formatting. It may be unlikely for an issue description to have phrases like noformat, but underscores, dashes, plus signs, and even curly braces are extremely common and are not suitable as tag markers in my opinion. I can easily think of when one might have an issue that gives code snippets like

      { start }

      code

      {end}

      and these should not present errors.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              6e88f3fc96e7 Neal Applebaum
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: