At the end of each quarter in 2025, a pop-up on the Atlassian Community forums appeared with a simple invitation:
“Tell us what you think.”
So many of you clicked, rated your experience, and then went further: you took the time to write comments about what felt great, what felt frustrating, and what you wished we’d do differently.
A few of you also asked a very reasonable follow‑up:
“What happens to this feedback? Do you actually use it?”
This post is our answer. It brings together:
The main themes we heard from your 2025 Value Analytics survey feedback
The changes we’ve already made to the forums
A look at what we’re still working on in 2026 and beyond
When we read the 2025 Value Analytics comments, a few themes came through loud and clear.
To start on the positive side, many of you told us that the forums are:
A valuable place to learn and get help with Atlassian products
A way to connect with peers facing the same challenges
A community where people are friendly, responsive, and generous with detailed answers
At the same time, you surfaced real pain points:
Too much outdated, unanswered, or low‑quality content
Difficulty finding reliable, up‑to‑date answers
Confusing navigation and search, especially around where to ask questions
Occasional “glitchiness” in the editor and UI
Uncertainty about when Atlassian staff would see or respond to questions
Concerns about privacy, identity, and recognition
Too many or confusing email notifications
Taken together, your feedback pushed us to:
Treat content quality and lifecycle as an ongoing responsibility, not a one‑time cleanup
Make it much clearer where to ask questions and how Q&A works
Fix editor, login, and notification frustrations
Improve profiles, privacy controls, and recognition
Polish the look and feel of the forums themselves
The rest of this article walks through what we’ve done so far and how it connects back to what you told us.
Many of you told us bluntly that too many threads felt outdated or like dead ends. In 2025, we started treating this as an ongoing responsibility, not a one‑time cleanup. We’re reviewing older posts more deliberately, archiving content that’s clearly no longer useful, and planning a larger cleanup effort in 2026 to retire more legacy threads.
We also added two new teammates, @Mohammed Shakhib (Content Specialist) and @Lukasz Modzelewski (Technical Community Manager), to help find, review, and remove outdated or low‑quality content. On any post, you can click “Report to moderator” to flag content that’s no longer accurate; that goes straight to this team for review.
You told us it wasn’t always obvious where to post or why some questions didn’t get answers. In response, we simplified the forums navigation and made it clearer that this space is for Q&A about Atlassian apps. The “Ask a question” button now takes you straight to the question form, so you’re not stuck choosing between confusing content types.
We also removed the “discussion” content type from product Q&A areas, because too many questions were getting posted as discussions and then overlooked. Discussions now live primarily in Groups, where open‑ended conversations make more sense, while product forums stay focused on questions and solutions.
A large amount of your frustration came down to one thing: the editor. You told us about copy‑and‑paste behaving badly and reply boxes jumping around in long threads. In 2025, we fixed an issue where pasted text would move to the bottom of a post, and another where the threaded reply field could appear at the top of the page instead of near the comment you were answering.
We also addressed a bug with @mentions sometimes failing after edits, so it’s more reliable to bring the right people into a conversation. We know the editor and mentions still aren’t perfect, and improving them is an ongoing effort for our team in 2026 and beyond.
Some of you used the survey to give feedback about the survey. The 500‑character limit in the comment box felt too restrictive, and several people pointed out that it wasn’t clear there was a limit at all.
In response, we updated the survey text to clearly state the character limit and added an option to continue the conversation via email if you had more to share.
Another cluster of comments focused on the basics: logging in, dismissing pop‑ups, and not getting flooded with email. Some of you ran into stubborn consent prompts that wouldn’t go away; others were seeing multiple notifications for the same thread or feeling overwhelmed by the volume of notifications.
To address this, we made login and logout more consistent across the connected experience (Forums, Learning, Events, and your Community profile), fixed an error that appeared when logging out from the Settings page, and streamlined the Notifications tab. The “Manage settings” link in the forums now takes you directly to your notification preferences, and we removed notification types that weren’t actually being used, so it’s easier to tune what you receive.
You also shared thoughtful feedback about how you show up in the Community. Who can see what, and how your contributions are recognised. Some people wanted more control over their public profile and photo visibility; others wanted their history and certifications to stay connected even if they changed jobs or email addresses.
In response, we launched a unified community profile that brings together your activity from Forums, Learning, and Events, with clearer stats for posts, accepted solutions, likes, kudos, courses, and certifications. You can now link multiple accounts, and we’ve updated privacy wording and behavior so your Community profile respects the visibility settings from your Atlassian account, including profile photos.
At the same time, we broadened recognition with new “Topics created” badges and refreshed Kudos challenges and badges so different kinds of contributions — asking good questions, sharing knowledge, and ongoing learning — all count.
Finally, many of your comments called out smaller UX issues that still made a big difference: headers that pushed content too far down the page, layouts that broke on mobile, and buttons that didn’t actually do anything.
Throughout 2025, we shipped a steady stream of fixes here. Navigation now does a better job of showing where you are, with sub‑navigation highlighting correctly and breadcrumbs navigation path and announcement banners displaying properly on tablets and phones. We cleaned up confusing elements like a non‑functional “Post in group” button in Community Announcements, fixed layout issues caused by very long usernames, and added the ability to give kudos directly from the author card on articles, making it easier to thank the people whose content helped you.
Several of you told us it wasn’t always clear when Atlassian staff would see or respond to questions, especially threads that are important to our members. In 2025, we created an internal report that regularly surfaces important conversations from the forums to Atlassian teams across product, support, and beyond. This helps us highlight urgent or trending topics and be more intentional about getting the right Atlassians to follow up where their input can add the most value.
Based on everything you told us in 2025, our ongoing priorities include:
Deeper cleanup and curation of older content, beyond the monthly removals already in place
Improved search and filtering to surface the most relevant, recent, and trusted answers
Continued UI polish for performance, mobile, and posting flows
We’ll keep running the Value Analytics survey each quarter, and we read every comment that’s submitted.
In the meantime, you can always:
Report outdated or inappropriate content via “Report to moderator” on any post
Use the “Was this helpful?” prompt at the bottom of the page to mark content as helpful or not. (This prompt may not appear on some smaller devices due to screen size.)
Share ideas or feedback in the Community Announcements group or email us at communitymanagers@atlassian.com.
Or respond right here: Which of these changes have you noticed? What would you like us to tackle next?
Thank you again for helping us make the Atlassian Community forums more useful, welcoming, and effective for everyone.
SilkeS
4 comments