✓ New portal experience is now default
✓ Improvements to agent queues
✓ REST APIs for managing agent queues
✓ Previous and next search results
✓ Self-protect and sleep easy with rate limiting (Data Center)
✓ Cluster monitoring (Data Center)
✓ Users and roles made better
✓ Custom changes transferred on upgrade
✓ PostgreSQL 10 comes to Jira
✓ Small improvements to make your day
New portal experience is now default
The new portal experience was already introduced in Jira Service Desk 4.1 – a streamlined redesign of the help center and customer portal that offers better layout and branding options. Existing users were able to choose the new experience or keep the old experience. Based on the positive feedback, Atlassian is making this experience the default for all new and existing users who want to install or upgrade to this version.
Improvements to agent queues
Agents can now easily find the most important problems by sorting their queues by column: Ascending, oldest, in alphabetical order. This is a personal attitude, so it won’t affect your teammates.
This is the first change to improve the queues. Also, keyboard shortcuts (arrows!) have been added to quickly switch between operations, and annoying errors with overflowing text have been fixed.
REST APIs for managing agent queues
While working on the agent queues, a number of new APIs have also been added that allow you to manage them outside the user interface:
- Create queue
- Reorder queues
- Get queue
- Update queue
- Delete queue
Previous and next search results
You can now quickly switch between search results by using links at the bottom. Instead of going back to all search results, you can go straight to the previous or next kb article (in terms of relevance). The new links are available on kb articles when you search from the Help Center or specific project portal.
Self-protect and sleep easy with rate limiting DATA CENTER
Without protections in place, automated integrations and scripts can hammer your Jira instance with huge bursts of requests, leading to drops in performance and downtime. This creates unnecessary work for admins who get paged (often after hours) to fix issues, and then have to comb through logs to find the culprit so it doesn’t happen again.
Rate limiting changes all this by giving your Jira instance the power to self-protect. Admins can now control the number of REST API requests automations and scripts can make and how often they can make them. This means increased performance and team productivity (and hopefully for admins, more sleep too).
Cluster monitoring DATA CENTER
Atlassian has extended the capabilities of the Atlassian Cluster Monitoring Plugin for you, so that it is now possible to monitor Jira clusters. This gives you more tools to manage your data center nodes.
To see the clustering information, go to Jira Administration > System > Clustering.
Users and roles made better
Atlassian has improved the “Users and their roles” page within the project settings for you. This should now allow project administrators to quickly add people to a project and assign them all the roles they need.
Now, it’s more about assigning roles to a user than the other way round. You can also search for users, view and select roles from a drop-down menu, and see everyone on a single list with nice columns explaining what’s what. You can check this out in Project settings > Users and roles.
Custom changes transferred on upgrade
Another upgrade hurdle has been removed: Now you no longer need to copy the modified files to keep your customizations after the upgrade. Jira recognizes the files you have modified and copies these changes to your new Jira instance.
PostgreSQL 10 comes to Jira
A new database among the supported platforms: PostgreSQL 10 is introduced.
Small improvements to make your day
New events in the audit log DATA CENTER
New events have been added to the audit log so that you can better track and manage what is going on in your Jira instance:
- Dark feature enabled/disabled
- Jira service deleted
- Project role created
- JMX monitoring enabled/disabled
New health check: JVM code cache
This check verifies that you’re using the recommended JVM configuration for code cache memory. Insufficient code cache memory can impact performance. If you’re not planning to upgrade Jira anytime soon, you can also get it by updating the Atlassian Troubleshooting and Support Tools (ATST) app to 1.30.0.
Stuck when searching for an issue because you can’t remember its exact name? Back in Jira 8.0 (Service Desk 4.0), we added a prefix search, which is now followed by suffix search. Here’s how to use it:
|text ~ “work*”|
|text ~ “*work”|
Timezone in logs
We’ve added a timezone identifier to date timestamps in all log4j log files.