The main purpose here is to utilize the Linux Cron facility to Transition Issues, rather than using the almost useless JIRA builtin services, or buying an expensixe cron/scheduling plugin for JIRA

The solution is pretty flexible for all issue types, by making the "--step "Initiate" a parameter instead of hardcoded, all issuetypes can be transitioned.

Prerequsites

Linux User

All scripts and the crontab stuff assumes that there is a "jira" user , with access to /opt/jira-cron/

Atlassian CLI

The Atlassian CLI must be installed and prepared

...

Upon the Transition of Initiate, the Post Function, creates a copy of the Issue as a subtask and sets the the issue back to Status "Frozen":

...

A custom Field for crontab values

The Issuetype has a custom field called "Cron Scheduling", as this will hold the schedules for the Issue:

In the script, the field has the JIRA identifier customfield_12821 - You must change this to fit Your field.

Location

I have my stuff in /opt/jira-cron

...