Best way of Scheduling automatic Issue Cloning or creating

[apoage]

Been looking at the Automation lighting bolt and it is prob one of the least user friendly things I have seen. All we want to do is automate the cloning of a bunch of our Patching tasks each month.  Going through the Automation stuff in jira I have tried a bunch of different settings but it never works. Dose anyone have a real guide on this? All the ones ive looked at here are not straight forward. They are just not good simple documentation. I dont see why something this simple would be so complicated to setup. 

[Craig Nodwell]

Hi @apoage welcome to the community.  For Cloning have a look at this post.

For managing dates have a look at this one.

If you're still struggling after trying parts of or modifications of these please send a screenshot with your attempts so that we can help guide you through to a solution.

[Clara Belin-Brosseau_Elements]

Hello @apoage, 

If you're willing to use a third-party application, I can suggest trying our Elements Copy & Sync app that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues. 

You’ll be able to bulk copy your issues each month while using Automation.

Don't hesitate to try our app, it's free during 30 days and stays free under 10 users.

Let me know if you have any questions.

Kind regards,

Clara

[Luka Hummel - codefortynine]

Hi @apoage and welcome to the community!

I'm Luka from codefortynine 👋

If you are willing to use a third party app, our app Deep Clone for Jira can help you with automating your issue cloning. While we don't support scheduled clones (yet) our app integrates with Jira Automation, enabling you to set up automated workflows that include issue cloning. Here's an overview on how to set this up (in a company-managed project):

1. Setting Up Automation with Global Looping Transitions (here is a more detailed how-to):
   1. Add a global looping transition to your workflow. This transition will be used to trigger the cloning process.
   2. Incorporate a Deep Clone post function into this looping transition. This function will handle the actual cloning of the issue.
   3. Create a new Jira Automation rule with an action that triggers this looping transition. This step is crucial to ensure the automation process starts correctly. When setting up this rule, make sure to add a regex to distinguish between multiple transitions to the same status and define a transition match with the name of your global looping transition (e.g., “Clone”)​​.
2. Avoid Infinite Loops: Ensure that your automation rule doesn’t create a loop that generates infinite clones. This can happen if the cloned issues trigger additional automations.

You can read more about different ways to use Deep Clone with Jira automations in our documentation.

If you need more specific guidance or have any further questions, feel free to reach out!