Jira Service Management 5.0.x upgrade notes
Below are some important notes on upgrading to Jira Service Management 5.0.x. For details on the new features and improvements in this release, see:
Upgrade notes
Breaking changes in SLAs
We’ve implemented the following breaking changes for the 5.0.x version and onwards:
TimeMetricHitCondition.getHistory(Issue issue)interface is changed toTimeMetricHitCondition.getHistory(Issue issue, DateTime until).Similarly,
TimeMetricMatchCondition.getHistory(Issue issue)interface is changed toTimeMetricMatchCondition.getHistory(Issue issue, DateTime until)
This is to cover the scenario where an issue might have an enormous backlog of SLA calculations to process, to such an extent that the earliest SLA metrics might be out of date by the time the last metrics are calculated. These API calls are for issue history-based calculation, and not event-based calculation, which remains the same.
The following are new interfaces that require implementation:
TimeMetricHitCondition.evaluateFromIssueHistory(Issue issue, DateTime since, DateTime until)TimeMetricMatchCondition.evaluateFromIssueHistory(Issue issue, DateTime since, DateTime until)
These interfaces are for use in ongoing issue history-based calculations.
Automation for Jira is now part of Jira Service Management Data Center
As mentioned in the release notes, Automation for Jira is now part of Jira Service Management Data Center. Here are some details you should know about.
Native automation in Jira Service Management
Jira Service Management already includes automation which is now being replaced with Automation for Jira. We’ve renamed the existing automation to Legacy automation and kept all your existing rules in place. You can continue to use them, but we recommend that you switch to the new automation engine, which has more capabilities and is easier to manage.
Upgrading information for existing Automation for Jira Service Management users
If you’re already using Automation for Jira as a Marketplace app, it will be automatically upgraded when you upgrade to Jira Service Management 5.0 or later. It’s important to check which version of the app you’re currently using:
If you’re using Automation for Jira 7.3 or later, you’re good to go.
If you’re using Automation for Jira 7.2 or earlier, there are steps you need to complete before you upgrade Jira Service Management.
For all the information about versions, licenses, and upgrade steps, see Understand versions, licenses, upgrades.
End of support announcements
For the list of supported platforms, see Supported platforms.
App developers
See Preparing for Jira 9.0 for any important changes regarding apps.
Upgrade procedure
To help you upgrade to the latest and greatest:
- See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps.
- For a more tailored upgrade, go to Jira administration > Applications > Plan your upgrade. We’ll recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.