Jira Service Management Server & Data Center 4.14 is now available!

[#1]

Hi Atlassian Community,

I’m Molly Bronstein from the Product Marketing team at Atlassian writing to you with the latest from our most recent release, Jira Service Management Server and Data Center 4.14. Starting from version 4.14, Jira Service Desk becomes Jira Service Management - and it’s so much more than a simple name change. Jira Service Management is an ITSM solution built for IT, Ops, and Dev teams to deliver high-velocity IT at scale. 

Here's what else is new in 4.14:

• New events to the audit log: In our Data Center edition, we’ve added new events to the audit log, including: 
• SLA conditions created
• SLA conditions updated
• Organization associated with project
• Organization disassociated from project
• JSM notification rule template updated
• Email channel updated (password changes)

Below are the new platform-level features available in 4.14:

• Email templates made better: You can now download email templates for your notifications directly from Jira, giving you easy access to all the files you need. 
• Set context for custom fields as you create them: We’ve made a few simple improvements that will help you set context for custom fields as you create them. Limit the number of global custom fields and keep your Jira instance in the best shape possible.
• Personal access tokens: Create personal access tokens, which are a safe alternative to using a username and password for authentication. You can create up to 10 tokens by default, and set different expiry dates for each.
• Embedded Crowd and password encryption: We’ve improved security with Embedded Crowd so all plain text passwords for external systems that have been stored in the Jira database will be encrypted starting from Jira Service Management 4.14.

Read the release notes to learn about other improvements shared across the Jira family and plan for your upgrade.

[Sajit Nair _Trundl_]

Exciting updates. Looking forward to using these. :)

[Dave Liao]

Good to see more JSM-specific events being written to the audit log! We need more configuration-level changes to be logged for audit purposes...