Issue Summary

Every time a Jira node is properly stopped, the schedules for this job is removed: com.atlassian.greenhopper.service.sprint.services.SprintAutoStartStopJob

While this makes sense for disabling plugins from the UPM UI, this may break important the functionality for those jobs whenever a node is stopped and not started again.

Steps to Reproduce

1. Set up a Jira DC with 2 nodes or more;
2. Check "Parallel Sprints" in Jira Software Configuration
3. Stop a node.

Expected Results

Everything remains working as normal

Actual Results

The job schedule for com.atlassian.greenhopper.service.sprint.services.SprintAutoStartStopJob is removed:

We can see Jira doing it in the logs:

2024-08-13 11:34:31,850 FelixShutdown INFO      [com.atlassian.greenhopper.Launcher] Unscheduling Jira Agile jobs...
2024-08-13 11:34:31,850 FelixShutdown INFO      [service.sprint.services.SprintAutoStartStopScheduler] [SPRINT-AUTO-START-STOP] Starting to unschedule a SprintAutoStartStopJob...
2024-08-13 11:34:31,853 FelixShutdown INFO      [service.sprint.services.SprintAutoStartStopScheduler] [SPRINT-AUTO-START-STOP] SprintAutoStartStopJob has been unscheduled.

Workaround

• When stopping a node permanently, stop it using

  kill -9 <pid>
  

• Or restart one remaining node after the removal. Jira will always create the schedules again when Jira Software starts up
• Disabling "Parallel Sprints" and re-enabling it recreates the job