I want to create a automation rule that creates +/- 100 recurring issues every month (monthly closing tasks for the finance department). Is there a way to import these issues once via csv to save them in the "then"-section of the rule? Or do i have to run the csv bulk import every month via automation rule?
Thanks in advance!
As the others already have mentioned, CSV isn't the right tool to create recurring tasks. Cloning template issues or projects might be a better way. If you are willing to use a third party-app, you can try Deep Clone for Jira. You can use Deep Clone for your use case in the following ways:
Clone Recurring Issues: After the initial setup, you can use Deep Clone to clone these issues for subsequent months. Deep Clone allows for bulk cloning and can carry over all the necessary fields, including custom fields, links, and attachments, making it an ideal tool for monthly recurring tasks.
Automate with Deep Clone: Combine Jira's automation with Deep Clone's capabilities. Set up a monthly trigger in Jira Automation that executes a Deep Clone operation to clone the set of tasks from a template issue or a previous month's issue. This requires manual setup for the automation rule to use a Deep Clone Post Function Clone via a looping transition, but it streamlines the process for future months.
It sounds automation rules won't be flexible enough here.
As an alternative there are two popular apps for Jira Cloud that offer "scheduled re-creation of an issue set". I think you should definitely try these:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Aron, I'll check out the possibilities of those two apps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Miriam - Welcome to the Atlassian Community!
You would need to do another bulk import every month - you can't accomplish that with an automation rule.
Or you could setup a Recurring process for your issues as identified in this article:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John
Thank you!
Solving the problem with recreating issues by cloning is a very nice work-around, thank you very much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.