Problem

In the documentation on How to change the interval or schedule of the DVCS repositories sync, explains how to set the interval. To do so, add an argument to the JVM arguments on startup to set the dvcs.connector.scheduler.interval property in milliseconds.
For example, if we wish to run the scheduled sync daily:
-Ddvcs.connector.scheduler.interval=86400000

Suggested Solution

Add an argument to the JVM arguments on startup<https://confluence.atlassian.com/adminjiraserver/setting-properties-and-options-on-startup-938847831.html> to set the dvcs.connector.scheduler.nextrun property in milliseconds.
For example, if we wish to run the scheduled sync daily:
-Ddvcs.connector.scheduler.nextrun = xxxxxx

Why This Is Important

The next run is changed every restart of the Jira server.

Since the business requires the restarts to always be at night, this is an issue that the restart changes the next run to time as it depends on the restart time.

Workaround

The only workaround provided is to change the next run directly in the database every time after Jira restarts.