You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Atlassian Community,
Alyssa here from the Product Marketing team at Atlassian writing to you with the latest from our most recent release, Jira Service Desk Server and Data Center 4.9 (full release notes here). Three quick highlights:
1. Reverting sharing settings for new requests: Back in Jira Service Desk 4.7, we’ve made requests raised in the customer portal private by default and allowed you to choose whether requests raised via email should be private or shared. We’ve gathered some feedback and learned that this wasn’t the best experience for our users, so we’ve tweaked it further in hopes of making it easier for you to choose your own defaults.
2. Improvements in SLA processing (Fix for JSDSERVER-6717): We’ve improved the reliability of SLA processing. By making changes to how events are queued, Jira Service Desk is much more resilient under high load. These changes are currently hidden behind a dark feature and will be enabled by default in the next release. If you were following this bug or encountered deadlocking when frequently updating the same issue, you can manually enable the dark feature now. Learn more
3. Cluster monitoring (Data Center): With the new information we've added to the Cluster monitoring page, you can quickly track and remove stale nodes and fix the failing ones in your cluster. This is because apart from viewing the ID and uptime information, you get the node status (active, no heartbeat, offline) and Jira status information (maintenance, error, running, starting). With this info at hand, venturing on any cluster clean-up task is way easier than it used to be. Learn more
Looking forward to hearing how the upgrade goes and your feedback on the more recent features in the comments below.