Updating an Escalation Service Job will trigger the execution of another Escalation Service Job

Steps to Reproduce the Problem

1. Create an Escalation service job with the cron expression '0 0 9 1/1 * ? *'. Add 'Escalation Service A' as Note for easier recognition.
2. In the Additional issue actions script editor, add

   log.warn 'Escalation Service A'

3. Create another Escalation service with the cron interval '10'. Add 'Escalation Service B' as Note
4. In the Additional issue actions script editor, add

   log.warn 'Escalation Service B'

5. Edit Escalation Service A and click 'Update'
6. Note in the logs that Escalation Service B is triggered

Expected Behaviour

Updating an Escalation Service Job will not cause another Escalation Service Job to execute

Actual Behaviour

Updating an Escalation Service Job triggers another Escalation Service Job

Additional Info

• SRJSUP-23374 Demo.mov
• Reproduced in
  Jira Software 8.13.11 | ScriptRunner 6.38.0
  Jira Software 8.13.11 | ScriptRunner 6.42.0