JIRA fields (specifically the Description field) doesn't display intentional extra spaces.

JIRA fields (specifically the Description field) doesn't display intentional extra spaces. Example:

EVTS Gold Service Upgrade - Emergency service dispatch

In the line above, there are two spaces that precede the word Emergency. These are important since it is the spaces that are the symptom of the bug being reported. When the issue is viewed in Edit mode, these spaces do show up. However, when the issue is viewed in VIEW mode, they do not. Therefore, someone reading the bug without opening it in VIEW mode, would not see the extra spaces.

Is there a way to fix this?

3 answers

It's just the way html is rendered. Use the preformatted/code macro if this is important.

Jira 4.4.3

The text entered is being rendered usning html and html removes spaces unless you tell it otherwise like it does here. I thought maybe a block qoute would work but it does not. The only way I found is to use the html sequence   to represent your space in Jira.

Click on the question mark below the descriiption box to see the allowed markup.

Try copying the line below into your description and use the preview button to see the results.

1             2

Exactly, it's nothing to do with Jira, it's your browser. Which is behaving correctly as it's not supposed to render standard white-spaces when there's more than one.

I would not go as far as it has nothing to do with Jira. Yes, the behavior is caused by the browser, but Jira could improve the situation by one or any combination of these ideas.

  1. Improve the documentation to warn users about this behavior.
  2. post process the text to translate spaces into   automatically within a paragraph
  3. Improve the online help to explain how to add spaces.
  4. Improve Jira's editor to include a markup notation for dealing with characters that do not render as people expect them to.
  5. Include a better editor into Jira
  6. Allow html editing in the editor.
  7. All the other possibilities I did not include!

Eh? You're asking for Atlassian/Jira to

  1. Document standards already globally published
  2. Work differently from every other editor on the planet
  3. See point 1 and 2
  4. See point 1 and 2
  5. See point 1 and 2
  6. Implement an editor which most people don't need and require them all to learn html
  7. See point 1, 2 and 6.

Sorry, but no. Point 6 has some merit - wiki markup is gradually receding in popularity as better editors become available (c.f. Confluence 4), but try looking at the internet - how much raw html is written by humans in an html editor nowadays? That would be a massive retrograde step for any editor.

Point 4 is covered by {code} macro.

The code markup did not work on our local copy of Jira, so that is why   was proposed as well.

Suggest an answer

Log in or Sign up to answer
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

58 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you