Community release notes for December 3, 2025

[#1]

Today we shipped some forum fixes and small enhancements. These include some improvements for our members that use the community from mobile devices and the ability to give kudos to article authors whose content you value.

Forums:

New: You can now give recognition to the author of an article from the author card. When you read an article you appreciate, click this button to give them a points bonus and an extra bit of flair for their profile. 

Updated: Subnavigation links are now highlighted blue when members visit the links.

 

Updated: We removed an unnecessary post button in the Community Announcement group to avoid confusion.

Updated: We made a small (but important!) text change on the Rising Star lozenge hover card. It now displays Community Champions instead of Community Leaders.

Fixed: If an announcement banner is displayed in the forums, it will now render correctly on smaller screens and mobile devices.

Fixed: Breadcrumbs now display the full path, improving navigation on mobile devices.

Fixed: Long usernames no longer break on mobile. The username, lozenge, and date display on multiple lines. 

As always, drop a comment below if you have any questions, feedback, or suggestions for the team.

[Bill Sheboy]

Greetings, community!

Is anyone else seeing these symptoms in the last couple of days worsening?

1. The notification feed (under the bell at the top right) often errors / shows as empty, and the feed does not show results until hours later
2. When one starts typing a post, and submits, its is timing out due to a page expire in under 2 minutes...forcing a copy, page refresh, and quickly paste and submit before it times out again

Kind regards,
Bill

[SilkeS]

Hi @Bill Sheboy  ,

Thank you for flagging this.

1. We do have an internal ticket open with our engineers to investigate the notification issue. Because it’s intermittent, it’s been a bit tricky to pin down, but we are aware of it and working toward a fix.
2. Are you still experiencing this behavior? When it happens, do you see an error message, or does the post just fail to submit? For example, it sometimes happens to me that if I’ve had the reply editor open for a long time before submitting, I need to refresh the page and then post again. Is that similar to what you’re seeing, or is it something different?

Any extra details you can share will help us track this down.

[Bill Sheboy]

Hi @SilkeS and happy Monday!

For the page expirations, I have not observed it again for about a week.  And, I did not notice any other errors other than the generic "page has expired...copy your content, refresh, and try again..." message.  The next time it happens, I will pause to check the dev console to see if there are any page errors behind the scenes.

Something which may help with repro is I do not use the email notifications, only the bell icon notifications to walk my "queue" of things to check.  My workflow is:

• open the latest Chrome browser on Windows 11 Pro 64b
• clear the cache
• log into Jira, the Atlassian Community, the Dev Community, the Support pages, JAC, and the Ecosystem equivalent of JAC
• observe there are notifications via the bell icon within the Atlassian Community
• select to open the bell alert, and right-click to open "See all notifications" in a new tab
• walking the list in newest-to-oldest order, open each non-duplicate alert in a new tab (which may be dozens of open tabs :^)
• starting with the oldest item first...
  • refresh the page
  • read it, and ponder my response
  • when I plan to post, refresh the page again to get caught up
  • reply and submit the post
  • repeat until caught up

When I notice I have taken more than a couple of minutes to compose a post, I copy it and preemptively refresh the page before pasting it back in to submit the content.