A year on from our forced migration on to Confluence Cloud and the lack of monospace formatting options remains a daily bugbear.

Almost every page in our knowledge base uses the noformat macro for displaying log outputs, ascii filesystem trees, etc. Whilst the code macro can be used for this, the inability to turn off line numbers is annoying and frustrating, compared to a simple monospace output:

|-~/.ssh/
      |
      |- authorized_keys
      |- config
      |- known_hosts
      |- idents/
           |
           |- host -> host.domain
           |- host.domain/
               |
               |- <login>/
                   |
                   |- id_rsa
                   |- id_rsa.pub 

More critical to our workflow, however, is the loss of the legacy panel macro, as this allowed us to format large blocks of monospace text with colour and highlighting to draw attention to relevant sections. Almost every page on our technical support knowledge base made use of this macro to reproduce terminal output. We have now been forced to use screenshots, which means the terminal output is not searchable.

Yep, this is awful.

There are some things that are visually attractive about the new editor, but so much useful stuff has been jettisoned or become less useful in the transition.

Atlassian keeps making it's products worse, line numbers are utterly crap.

Worst of all, if I select more than one line with the mouse , to insert it somewhere else like a terminal, the X11 selection contains the line numbers! That can mess up shell snippets VERY dangerously and lead to destruction of data! PS: This does only seem to effect Chrome, not Firefox, sigh.

Maybe we should create makros, we have one other idea already too.

PS 1: The "expansion" thing provide a workaround, but a bad one because it looks wrong with a proportial font and worse with code-style (Ctrl-Shift-M) which creates a gray background word by word or line by line.

PS 2: The old editor still have the "noformat". We will try to create a macro for the new editor, if we do we'll make it free, promised.

PS 3: Why is there no permlink for comments any more?

As an alternative, this can be achieved via a clumsy workaround using the /markdown macro. Inside that macro, 4 or more spaces at the beginning of the line will turn text into verbatim format, which seems to have the same net effect as using /noformat in the past.

Triple backticks inside the /markdown macro works as well, although the result does not seem to be as consistent.

Update: the result is not the same because this workaround will do line wrapping, unlike the /noformat macro.

It's the same in Jira Cloud editor, right? I don't see a way to enter a noformat box; just the code box (and no way to remove the line numbers from this).

This is important for my team.  I use the noformat tag all the time for log file snippets.  This requires monospaced font and ignoring all formatting, but I don't want line numbers.

Edit: I just noticed this works here at jira.atlassian.net.  How do I get it to work on our team's Jira? 

here is a box with no formatting

Yes, I'd definitely like to see this back.  I was just in Jira Service Desk trying to nicely format screen output from a shell, and Google led me here.  I had to settle for the new ```code block``` notation, but I really didn't want line numbers.

Alternatively, there used to a a few { terminal } macros the mimicked something similar.

I don't see a way of entering unformatted text. There is "Code", but what if it's just a shell output, not code, and I don't want line numbers? Please bring back the:

{ noformat }