Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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.


Gregory Van Den Ham
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 23, 2017

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.

Like # people like this

I would assert its not anyone at Atlassian who should be asserting what paying customers confluence sites look like.  Imposing a layout, removing tools to design layouts as desired is simply a disregard for your customer base.  Whomever is driving customer experience should be taken to task.  This is not Wordpress!

I have been watching the evolution of Confluence since very early on and progressively the tools to fully control how content is presented and ability to nuance structure erode with each successive release. First you introduced the Wysiwig editor (and kept the wiki markup (a la but then you changed your storage format and too bad for those who liked wiki markup.  Then the macros slowly started to disappear..  etc. etc..

If the desire is to provide layout options to the user base that's one thing but forcing a single view and removing the ability to control layout and related tooling creates discontent for your loyal fans. Making it easier for some at the expense of removing tooling that has built a loyal fan base is a questionable strategy which could come back to haunt. 

Like # people like this

Interesting Post by Atlassian about sunk cost fallacy.. from all the feedback I have seen about the new editor.. it might appear that the sunk cost fallacy is at work within Atlassian .

Like # people like this

This is maddeningly condescending: "there is always room for comment... improvement".  Those sweeping platitudes might be informative if your audience is a five-year-old child but it's a terrible dodge in just about any other circumstance. 

Confluence remains the horrible, disorganized tool it's always been and honestly if it wasn't bundled with Jira (a much better offering for its purpose) nobody would use it, even if it was free.  To say nothing of the ugly results. 

Is it simply incompetence or indifference to glaring issues? More likely (speculating) a wholly unmaintainable code base that makes extending or improving it a re-write candidate? I doubt it's money, which really leads me to believe the code is an impossible mess. 

Like # people like this
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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.

Like # people like this
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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.


Like # people like this
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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.

Like # people like this

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.

Like # people like this

Any updates on editor improvements?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 07, 2018

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

Like Micheal Planck likes this

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

I guess this has become of less importance for Atlassian. We see the WYSIWYG editors all over the place, MS Teams is one of those which cannot handle a simple code block anymore. A selling point for CEO-level PPT/Excel operators.

My company is transitioning away from Confluence for technical docs. We are going to use reST, Git, and Sphinx to generate the documentation anyway we like. Partially but not entirely because Confluence has become a time hog and a source of frustration.

I'm still after 5 years of using Confluence from time to time at various places confused why I always get an extra space character at the beginning of a cell in a table. Is that a feature or a bug?

I still like Bitbucket though, hope Atlassian can focus on that one! :)

Like Micheal Planck likes this

Agree. The Confluence editor is HORRIBLE. Almost unusable. Really thinking of scrapping Atlassian entirely over this one issue.

Like # people like this the issue is the elimination of options.. Adoption in an organization has little to do with using the editor and the cheerleaders in the organization reap considerable agility and prowess when you provide powerful tools like wiki markup and a powerfull suite of macros.  Now adding options is great but if you take away the tooling of the power user, now you handicap your most loyal fans with a nonsensical view that users will flock to Confluence cause the editor is wysiwig?  The power of Confluence is the dynamic liinking, collaborative content, some of the powerful macros and the flexibility to organize content to suit the ever changing perspectives different stakeholders  adopt.

The adoption problem is that the world has been numbed by MS Office, Sharepoint and the like...  a problem I refer to as "Knowledge Islands".  Most people are unaware of how isolated they have been packaging their knowledge and as such failing to benefit from it. 

If the goal is to address Adoption then perhaps a page from the VMWare Fusion playbook could yield considerably better results without alienating your loyal base... What about a tool that migrates a sharepoint site into a confluence space?  Or creates meta indexes of the file structure (maybe even extracts a bit from each file in an attempt to assist reader?)  Any such approach which would "re-package" knowledge islands into a form which could be collaborated on, dynamically referenced or illustrate other valuable capabilities of Confluence (and or other Atlassian tooling) would be a neon WOW compoared to the "metoo" wyswig checkbox.

Atlassian has had some great tools in the past and unfortunately successive releases of Confluence are being handicapped...

Most of us power users are your biggest cheerleaders for adoption in the business world, help us out instead of handicapping us.  Lets focus on the why challenges of adoption: I have found that most people don't work in collaborative ways, and once a person begins to incorporate collaborative work habits, their appreciation of Confluence explodes.  in the 20+ years I have been a wiki cheerleader wysiwig has never been the obstacle..

Like # people like this

Whatever the motivation, the new editor is plainly vastly inferior to the old : dumbed down and inflexible.

So why can't the old one just be allowed to continue alongside the new ?

Like # people like this

I have seen Confluence at every software company I've been at.  We want to direct executive sponsors, core team members, the extended org and all stakeholders to it.  But - for engineers, project managers, product managers, product marketing, QA, doc and more it becomes the great black hole that no one updates or they add content that never is seen again.  Maybe our bar is too high because of all the great WYISWG page building tools out there for the past decade, but unfortunately Confluence has become the "thing" you buy to centralize info in a structured way regardless of ease of use.  My new team spends a crazy amount of time trying to tweak pages to look somewhat professional.  I would have expected this frustrating experience 20 years ago, but in 2019 I am flummoxed.  I am sure there are things behind the scenes of Confluence that are beyond my understanding but the reality is that we feel like we are stuck with it.  We should not be pulling out hair to create bulleted lists on a blank page, trying to add spaced between numbers items and the beginning of the text, trying to use a layout for your page this is either "too narrow" or "way too wide", trying to reduce the uneditable number of pixel lines/wasted space in the Jira roadmap macro - and that's only the beginning.  What ever happened to "drag and drop"? We've followed what would logically be steps to edits pages, sidebars, text, links etc and go round and round to the same dead ends.  This stuff should be simple and intuitive.  I can more easily create formatted Slack messages than create a simple formatted page in Confluence.  Finding good answers in the vast help systems is laborious and most often the accepted answer is incomplete, it points you to somewhere in the product that doesn't exist OR it seems like you are supposed to write code.  Maybe I am just not the target customer that work is prioritized for.  Then there's all the super basic missing features in "Next Gen Jira", but that a different story.  I would be so happy if someone would sell a totally basic structured content tool (replace confluence) that completely integrated with gdocs (the sharing and live editing is unmatched) with something a little more advanced than Trello (basic kanban or scrum with ticketing).  Integrate those all without forcing customers to write code to do it and you've got 80% of the capabilities the average customer needs.

Like # people like this

I have used Confluence and Jira in most of my consultancy projects since 2007. This is coming to an end unfortunately because of the editor in confluence. We are now not able to link to images so we can actually make pages that look good with clickable icons and the ability to have panel without any icon is gone.. Even at some point we could not even use the full screen for our confluence pages.

These two products are getting worse by each release. It is really sad to see. Reminds me of old IBM development tools that got bloated and worse year after year, and now those tools are dead.

We are now looking for alternatives that can serve us better

Like # people like this

If you find something, please let me know.  I have many friends in tech who want to jump ship.

Like # people like this

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

Like Ray Myers likes this

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.

Like # people like this

Numbered lists are unusable.

Like # people like this

@Jeff_Kelly esp if you want to put and image inbetween a step. Absolute nightmare. I've taken to manually typing them.

Like # people like this

I can't even get numbered lists to work with an entry that is a nested list - the outer list always ends up restarting the numbering at 1 for the next item after the one with the nested list in it!  This stuff is trivial if you use a mark up language instead of the dreaded WYSIWYG.

Like # people like this

Funny, I was JUST struggling with the same thing :) 
Brutal stuff.

Like Alan Akins likes this

annnnd that is how I found this post.  I have used MD and wiki markup before.  They had their issues, but it was logical and I could usually find a fairly straightforward way to get the results I wanted.  However, with the WYSIWYG, I can't get anything close.  My organization had the self-hosted version and I learned how to format our documentation fairly well using it, but now since we transitioned to the Cloud Confluence it is almost impossible to get anything close.  Now I'm left debating on creating documentation that will be 10x longer since the numbered lists won't work with any other formatting (e.g. expand).

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.

Could not agree more with these sentiments. One of our project managers has begun an initiative to migrate our github wiki pages to confluence, and the contrast between the two editors, in both ease of use and features, is staggering.

I would not hesitate to describe the experience as "soul crushing".

Like # people like this

We just use Google Docs for collaboration and use Confluence cloud to publish. However, we are looking at other options as we keep running into unforeseen obstacles - base functionality are paid for add-ons, just learned anonymous access to Confluence doesn't play well with Jira access, etc.

So, there were text entry experts who used markup to get their work done and novices who tried to use markup because the WYSIWYG editor was unusable. And Atlassian's solution to the novices' frustration was to remove markup to focus on WYSIWYG? Best case scenario: the novices are happy, and the experts get can't their work done. It's mind-boggling.

I want to edit my documents in Vim. No WYSIWYG will come anywhere close in convenience. Especially not a laggy web app.

Like # people like this

The editor is the most counterintuitive thing ever. I can't type or format anything. For example;


- The undo (cmd + z) does not undo the previous changes. No, it goes 3 changes back???

- When I have a list and I want to remove the indentation of 1 line, it transfers my current line to the previous line. Even if the line above is a code block. It transfers the line INTO the code block. Why would anyone want that? A code block should be a self-contained thing and nothing to do with the rest of the text.

- Inside a code block when trying to select everything with the all known global shortcut cmd + a, it selects everything in the entire page. Why? Just why???? Again it should be a self-contained thing. 

- Trying to indent something with tab does not work and you rotate with all the functions in the toolbar. But only when you have an indentation then it does work. 

- Lists are just awful. When editing a list it does nothing that you think it does. Backspacing on a bullet point, let's go to the previous line (wtf). And when you try to undo that, it undoes the previous 4 changes that you made. 

- The shortcuts for deleting words (alt + backspace) and deleting lines (cmd + backspace) never behave as you want. Deleting lines does not clear the bullet point and deleting words does not adhere to most common word breaks.


I can go on but I'm having a hard time not to curse and scream when thinking about it. It takes me sooooo long to format it. I understand for your average Joe it might work but I don't know if your average Joe is the one you should focus one. I really don't know how people work with this or if the creators even try it themselves. Even writing in HTML is faster and easier than this. 

Like # people like this

So agree. And very unhappy that I recommended to a brand new customer that we do all the doc work in Confluence. I feel I just hurt that customer.

Like # people like this

Ha Ha Ha... even here things are broken. When I made the reply above, my name was shown. Now I am "full_name", though I think it should have been spelled with an 'l' instead of 'n'

Here I am, 2021 and these problems are all still here. I believe Mind boggling is the word Ive seen here a few times... so true. I actually have a text editor that I wrote my notes into and then copy and paste it into the Confluence pages. Constant thorn in my productivity. Have they done user testing on these new features or do they just send it straight to development? starnge so many agile teams use Jira products, does Jira use AGILE structure when developing their products? Trust your users.

I cannot figure out how to make a nested list.


This is not a complicated document structure by any means, I remember being taught how to create document drafts in this manner at around 10 years old in school. If I had been forced to use this editor, I would have failed that unit.


Absolutely unacceptable.

Like # people like this

I've had fairly good luck creating raw list markup in a text editor (a la VSCode), and then inserting it into Confluence's rich text editor via Insert > Markup. Nested lists created directly in the RTE fall apart when the browser is resized. Using this method for some reason creates something different and it works well even when the browser is resized.

* Level 1 entry

** Level 2 entry

** Level 2 entry

* Level 1 entry

Etc. The imported lists then seem to remain stable when edited directly in the RTE.

The WYSIWYG editor is total garbage. This debacle has been going on for years! Shameful. Better tools must exist at this point (then anything by Atlassian, if they continue to inflict this editor upon us.)

Like # people like this

Have to agree with everyone here.  Most frustrating editor I have ever used!  Please fix or replace it!

Like # people like this
Like # people like this

The confluence WYSIWYG editor is complete and utter garbage! This has been going on for years! What a complete debacle. Atlassian is completely wrong on this one! I have been struggling for hours to create a very simple document that takes me literally minutes in github. Absolutely unacceptable that Atlassian continues to support this steaming pile of crap. Just read the comments! Everyone hates the editor, wake up Atlassian.

Like # people like this

Clearly people who know markdown dislike the WYSIWYG editor; why not let us type in markdown? Make it some obscure setting if you don't want to confuse novices, but at least understand that your audience is using GitHub regularly and finds this editor to be vastly inferior to just typing the markdown themselves. Frankly, the comment box I'm typing this in is a superior experience.

Like # people like this

Just wait until you see the new ...

Like # people like this

i want so much to like confluence because of how well it can solve some problems but the stone age formatting capabilities makes it a hard sell. then the world of macros and add-ons that would make up for the deficit are essentially not there due to the unrealistic permissions requirement that prevent many cloud users from having access to them. so it's rather a shame to see Atlassian being blind to an enormous market opportunity .

@Bruno Bronosky for how long have you been using Confluence? I'm asking this because recently they tried to deploy a dumbed down Editor and it was a failure, I think in part due to feedback of people who say it was too complex.

If anyone thinks the current editor is too complex what does the same person thinks of the Word Editor? My suspicion is that you haven't used Confluence at all and that kind of feedback makes product owners try to dumb down the product which ultimately results in utter disaster.

I have been using Confluence for technical documentation for the last 4 years and I love the current editor. It's simple, effective, uncomplicated and layouts give you a lot of freedom.

if you want a page to look beautiful its going to give you a little bit of work, but that's it, then you have a template you can reuse many times over.

Try to open your mind a little bit and use the Confluence editor to understand its features. Look at examples and you will see it is actually very effective.

Like Thomas Kreft likes this

Joao, what does MSWord have anything to do with the confluence editor?


People aren't complaining that the new editor is too complex. They're complaining that it is actually just broken. Because it is, completely broken.

Like # people like this

Not only is it broken, it takes far longer to produce documentation with a WYSIWYG editor as compared to mark-up (my own experiments say 4-10 times as long).

Like Clifton Foster likes this

This is absolutely the worst document editor I've ever tried to use.

Like # people like this

It's grotesque

The confluence visual editor is probably the worst thing I have ever had to use to produce technical documentation. Even the horrible Word does a better job.

I can't even create a `preformatted` text consistently. Sometimes the backticks work, sometimes they dont. Copy-pasting text from other sources breaks the formatting even though it's just two words with no special characters or line breaks.

I've just spend over 15 minutes to produce two lines of text and still was unable to format it the way I want to. 

Using confluence editor is easily the most frustrating experience I ever had producing a document.

Please, please, let us write in markdown! 

Like # people like this

It is obvious that Confluence can give a rats @55. They haven't responded in months.

Like # people like this

Cannot upvote this enough.

Like # people like this

I recently found the updated editor option and admittedly it is much better.

Where did you find that and what version of Confluence Server/Cloud are you using?

Looks like this has been an ongoing theme for years??

I would think that companies would listen to their customers and offer what they are looking for.  Oh wait, customer service went out the window years ago and we must conform to what is provided and not what is requested / wanted by the customers.

I'm trying to center a table that has 4 columns and 13 rows that includes a header row.

I can't seem to find an easy way to do this, Indenting doesn't work, The Centering option doesn't work.

We shouldn't have to add a bunch of add ins or macros in order to complete such a simple task.

If I had on option to use any other application I would, but I don't, this is the Application our company chose.

Like # people like this

I agree, this editor is the worst. I just want to make a nested list. Seems impossible, Reading the comments here make me want to give up.

Like # people like this

Is there an official plugin that allows users to just choose their editor of choice when creating a page in Confluence? 

Checked and I am using which does the work

Like Daniel Everett likes this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events