🗓️ Save time by scheduling work in Jira

[Hercules Konstantopoulos]

@Eoin just jumping on this cadence comment: it would be rad if we could get the same calendar functionality as we have in Automation with the 'Scheduled' trigger: 

[Robin Powell]

@EoinWe don't really use due dates, so the value for us would just be in the creation of the issue.

[Lianne Geerlings]

@Eoin  My work items are mostly related to monthly or annual checks.  For me creating the work item every month will give me value.

[danielwould]

I thought I might chime in here, since I'm happy to see the start of an 'official' support path for recurring tasks, having built out automations for this myself, I'm always keen to drop custom implementation. However as noted it seems this version is still a little primative.
I handled this by introducing labels for WeeklyTemplate, MonthlyTemplate, QuarterlyTemplate and an association automation rule that runs weekly/monthly/quarterly that looks for issues with that template and clones them, removed the label from the old after it has a new 'latest'. It also creates a 'cloned link' relationship between the old and new.
this relies onf also having an automaiton on issue create that can tell this is a cloned eg story - so that it can query the clone source to find the subtasks then also clone those. which is a bit of a faff but works arond the otherwise inability to clone a task and it's subtasks.
The advantage here is that I have 1 rule per reoccurrence rate not lots of different ones.
to solve the isue @Eoin mentioned about targeting the right day - I introduced a single new field 'T-Plus' so that an issue states how many days past it's reference point (start of week/start of month etc) it is supposed to be due. I can then use the built in business days feature to figure out which date is that many business days into the target period.

I go another step further to auto create reocurring epics that 'own' all the recorrding tasks in a given month so that when I spawn new issues I look for the epic that start/due spans the target reoccurance date and link them. So the team can easily manage each batch of reoccuring tasks.

Whilst this was a little complicated to setup initially, it has been running very well for several months. I'd love to see a native jira implementation with a lot of the same capabilities that allows me to decommission custom logic.