The Confluence editor is TERRIBLE. What can be done for cloud/hosted customers?

Does this feature cause more work than it saves?

This is a question you should always ask yourself. It is clear that the Confluence editor team has never seriously considered this.

The Confluence editor regularly creates 12 times as much work for me than a plain text document. Where possible I write documentation on Stack Overflow or create a gist on github and link to that. I have many unfinished documents that never get published because I can't get the formatting to not suck.

What can be done? Why does Atlassian not do something about this? There is no way that they use internally, what I am paying for, without hating it.


There's always room for feedback, and room for improvement.  Cloud has some limitations because of the way Atlassian maintains and upgrades that environment.  The need there is to be consistent across many instances.

Have you thought about providing the founders feedback?  You might get a response - but certainly, I'd suggest proposing a solution with your feedback so they can take that back to the team and make change happen.

Phil Oye Atlassian Team Oct 23, 2017

Thanks @Bruno Bronosky for the feedback. I'm a product manager on Confluence Cloud and I look after the editor.

The editor is an area of intense focus for us. We are in the process of rolling out some changes now, which you can read more about in this post here on Community.

But we're not stopping there, we feel your pain and are actively working to address it. 

If there are specific bugs, you can help by reporting them via Support

The bug is that no WYSIWYG editor has ever worked. They all fail. A rich text document is a data structure. We need to be able to see and edit that data structure in order to effectively communicate our intend to the rendering engine. If that data structure is Markdown, let us see and edit the Markdown. If that data structure is HTML, XML, or something more unintelligible, we need to be able to edit that (however, you may want reconsider how you store your data).

What you must not do is rely on inference of intent. You cannot accurately infer. You must empower us to tell you our intent.

Phil Oye Atlassian Team Oct 23, 2017

[Copying my response to your other post]

Thanks for your feedback about this.

We introduced the rich-text editor as the only way to edit content back in 2011. Our goal then, which is unchanged today, is to ensure Confluence is suitable for everyone in an organisation. We found that editing markup was the number one barrier to adoption.

Before we maintained a dual-editor experience (rich text vs markup) and it caused huge issues for our customers, had even more bugs, and prevented us from introducing advanced editing features.

We still believe we made the best decision based on the feedback we received from the majority of our customers over the years. The rich-text editor is our path going forward.

We know that it our editor isn't perfect, but we are committed to improving it to ensure all teams can collaborate in Confluence.


I strongly disagree with your assessment. The removal of the wiki markup editor was a HUGE problem for us and has greatly increased the time it take for us to create our content.

If the dual editor has more bugs that is not the user's fault. That is Atlassian's problem and we should not suffer because of your inability to fix those bugs.

I'm sure some users like the new editor, but please don't generalize by saying that this is suitable for everyone because it certainly is not.

Also, your user community board blew up back in then, just as it did a few months ago when you changed the interface for the Cloud users. Unfortunately, your Atlassian's response was the same back then as it was this time around - a little lip service and just allowed time to pass so it would die down.

Thanks for listening to one more dissenting voice.


Phil Oye Atlassian Team Oct 26, 2017

Thanks @Sandy Johnson for pointing out the everyone is much too strong a word. I would update it to say "to target as many people as possible in an organisation".

Wikimarkup was great for some people, but unfortunately, not so great for many more, hence our decision.

Thank you for the direct feedback, it is important for us to hear it.

I don't care about wikimarkup versus anything else. What I care about is precision. If I, as an engineer, cannot specify to your application precisely where I want formatting to start and end, then your editor is not suitable for everyone. I would posit that it is not suitable for anyone because I don't know anyone who will exert as much effort to solve a problem as I do. This editor is suitable only to those who settle for what they cannot change. If you want your tools to be accepted by people who write software for a living, you cannot say to them, "those same pseudo-technical people you argue with in meetings were struggling with the editor so we brought it down to their level by stripping away what made it useful to you.

By the way, if I want to insert an inline code block, I'm going to do it whether your tool allows me to or not.

  1. If I want lists
    • with lists inside them
      • with lists inside them
  2. Yo Dawg!
  3. That's exactly
    • what I'll get

What I'm trying to say is that it is in your best interest that you find a way to empower others and make life easier on people like me while you are at it.

BTW, in order to get things as simple as <code> blocks for the inline code block above, I had to use Chrome Developer Tools to edit the DOM of the TinyMCE iframe. Some changes require that I alter the tinyMCE javascript object in memory to edit the valid_children, valid_classes, valid_elements, and valid_styles. It should not be this difficult.

Any updates on editor improvements?

Yup, this was asked a year ago.  Atlassian has moved on.

Ah, so there's no scheduled changes to allow editing for of a markup language then?

Ted G I'm New Here Jul 17, 2018

Its literally the worst editor I've ever used in my 25 years of being an Engineer.  What I do now is just open the source editor and make my edits that way.  At least there I can have some control over the formatting.  Ill type a few lines (that it for some stupid reason wants to double newline) then ill save it and it will randomly pick a line to triple newline.  Its like WHAT?!  Its absolutely horrendous.  

Agreed. Absolutely horrendous. Can not believe how many customers have to suffer using it. Linking to a gist on github is a perfect solution. Feel free to close the ticket

Confused: if I have to link a Jira issue to github so I can make clear communication on an issue description or comment, why would I use Jira as my issue management system? 

The worst specially with lists.

Completely agree with the most recent few comments. 

Users should not have to essentially write code to create a description or comment on an issue.


Log in or Sign up to comment
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

490 views 7 6
Join discussion

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