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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence Cloud bug backlog is getting cleaned up 🪲

Hi Confluence Community,

My name is Sai Ramanathan, and I’m a Senior Engineering Manager on Confluence Cloud. The Confluence engineering team is continuously working behind the scenes to fix bugs, in addition to delivering new features shared on Community.

Over the last couple of months we’ve been focusing on prioritizing fixes for the most painful experiences for a majority of Confluence customers. We are in the process of streamlining our bug backlog.

This will be helpful because:

  • JAC ( will be more representative of our actual bug backlog, since it will include only reproducible bugs

  • An up-to-date backlog will reduce noise and make it easier to surface and find high impact bugs

We will be continuing this effort over the next several quarters. As such, in the near future:

  • You may notice updates on bugs you’ve voted for or are watching.

  • Some of these updates may be requests for more detailed information about reproduction steps in order to help us identify if they are still an issue and prioritize accordingly.

  • We will be closing out bugs that cannot be reproduced or that have had no interest/votes/comments recently (after allowing a couple of weeks for your input, response with additional details where relevant). If you disagree and believe a bug is still impacting your team, please let us know by commenting on the issue.

  • We will be closing out duplicate bugs and re-directing you when necessary to the relevant open bug.

Thank you for your continued patience, engagement and understanding as we work through this process of making Confluence Cloud better for all of our customers!

As a reminder, you can see the recent bugs we’ve fixed here and our upcoming Roadmap for new features.


Jack Brickey Community Leader Dec 02, 2022

@Sai Ramanathan ,

thanks for keeping us in the loop. I need to take a fresh look at those I’m interested in and will comment with any updates. 

Like # people like this
Andy Gladstone Community Leader Dec 13, 2022

I echo @Jack Brickey appreciation here. Anything to clean up the backlog, even an answer that the request/bug/issue is not a priority/not on the roadmap is an answer and will make navigating the large number of tickets and requests easier. As I am always told "No" is also an answer!

Like Valerie Blondel likes this

Good news...what about Jira :) 

@Sai Ramanathan 

Thank you for the effort you and your team puts into making Confluence even better. I can only speak for the users in my organisation, we use Confluence as a very important part of our knowledge management. We are very willing to support you with quality input and feedback to make your work more fun and rewarding, we know that getting only negative input as "this does not work" can be a little frustrating at times.

Greetings, Harald

Like # people like this

Personally I think this is just a whitewash.

You've got bugs going back 4 or more years that have not been fixed.

You have obvious bugs - such as numbered lists which won't continue numbering when something such as a code block or table are added in-between, or font size failure on /excerpt simple text. You have page layouts that are limited. etc..etc..

But worst, you have a bug reporting policy that assumes everyone who's interested will report a bug and thereby increase the number of reports to an actionable level. You also have bug reports that are similar, so individually the same bug receives less hits.

You fail to address issues that have a big impact on documentation and continue to pump out obscure improvements that have limited application. 

You ignore many comments on your failure to resolve issues.

You have a blinkered approach to bug management and have unrealistically high requirements for bugs to be accepted and resolved.

You refuse to engage with users.

You send out questionnaires purporting to engage with the users but which actually are slanted towards positive marketing only. 

You seem singularly incapable of understanding the working practises of your user base, resulting in a tool that provides limited functionality and party baubles.

Like # people like this

Very glad to read this, but am curious if this will be followed through. I must say i do understand a reaction like from @Nicholas Wade , and i hope you don't take that personally but as a sign as how at least some users have experienced Atlassians operation up till this point in time. Really (!) hoping this is a change for the better. Must be a lot of info/bugs to go through, so all the best with that, and looking forward to seeing bugs getting fixed (just today again experience you can't paste a picture in a bulleted list and have it stay sticked to the bullet you're in, instead getting pasted at the end of the bulleted list).

Like Ícaro H_ likes this


Log in or Sign up to comment

Atlassian Community Events