Duplicated Escalation services after upgrade to 5.3.0

Upgrading to ScriptRunner version 5.3.0 and editing an escalation service - duplicate services are created.

Steps to reproduce.

• Create an escalation service with SR v5.2.2
• Upgrade plugin to v5.3.0
• Edit the additional actions in the escalation service and click update

In the UI everything seems as expected. But if you wait for the service to trigger you will realise that, editing just created a new escalation service and it did not replaced the old one.

Now navigate to Built in Scripts -> List all scheduled jobs and you will see two services.

Workaround

Run the following script via the script console

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.scheduler.SchedulerService
import com.atlassian.scheduler.config.JobId
import com.onresolve.scriptrunner.runner.ScriptRunnerImpl

def serviceId = "-791361140" //replace with the id of the job as listed in  List all scheduled jobs (see screenshot)
def JOB_ID = JobId.of(ScriptRunnerImpl.PLUGIN_KEY + ":EscalationService-job")
ComponentAccessor.getComponent(SchedulerService).unscheduleJob(JobId.of(JOB_ID.toString() + ":${serviceId}"))