Improved functionality for scheduling recurring activities

[Alex Cook]

Some of our teams have a lot of regular activities that they need to do on a schedule - things like installing updates, running reports and so on.

Some of them are daily tasks, but others may be weekly, monthly, quarterly or even annually.

We've done some testing using the standard "Set to Recur" and while that works ok, it's not particularly flexible, and is a real pain when it comes to troubleshooting the recurrence. You end up with dozens of Automation Jobs all called "Clone on a schedule".

Are there any good add-ons that will make this process easier? We'll still need to create a template ticket for each activity, but having the ability to generate a whole bunch of instances of that ticket for the year ahead at a defined schedule with a few clicks would be a great help.

We'd then be able to add them all to appropriate future sprints rather than wait for the latest instance to be created as the last one is completed.

Thanks

[John Funk]

Hi Alex,

Take a look at this article and see if it helps you:

https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

[Trudy Claspill]

Hello @Alex Cook 

Rather than using the "Set to Recur" option you could use bespoke automation rules designed to meet your requirements.

If you are not familiar with creating automation rules you can find Templates available  within the Automation UI that may help you get started. There is also free, on-demand training available through the Learning link at the top of the Community pages.

https://community.atlassian.com/learning/catalog?product=Jira&search=automation+rules

There's also the documentation provided by Atlassian:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

If you have an existing task to use as a template, you can create an Automation Rule to Clone that task. The rule could be triggered manually or set to run on a schedule. You could clone the task once or multiple times. The details of the rule would really depend on the specific requirements of each scenario you want to implement.

If you describe the requirements of a particular scenario we can offer more targeted advice on how to implement that scenario.