create recurring task
Asked by Marie-H?l?ne PARISATO:

hi, i have the same issue : be able to create a task and be able to ask for clone this task according a frequency that my user will choose.

<br />

The response i have been done is to create a rule in automation with scheduler.

Use automate rule with scheduler is not a good solution for me because :

- i understand that the schedule will run the rule every month for example to create tack.  
- i want to see now (or just after having ask for rule) in the calendar all of the new task created by rule, You see.

Do i do a mysunderstood ?


Answers:
author: Luka Hummel - codefortynine
body: Hi [@Marie-H?l?ne PARISATO](/t5/user/viewprofilepage/user-id/4508655)

I'm Luka from codefortynine.

If you are willing to try a third-party app, you can try our [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2720965).

Deep Clone allows you to clone an issue multiple times.

![2024-06-12 15-25.png](https://community.atlassian.com/t5/image/serverpage/image-id/329478iD8D3CC03195F629D/image-size/large?v=v2&px=999 "2024-06-12 15-25.png")

You then can use[our Field Editor feature together with our custom *cloneMultipleTimesIndex* expression](https://documentation.codefortynine.com/deep-clone-for-jira/jira-expressions#CloneandEditWithJiraExpressions-CloneMultipleTimes) to have Deep Clone set ever-increasing **Due dates** with the following expression:

```
issue.dueDate.plusDays(7 * cloneMultipleTimesIndex)
```

![2024-06-12 15-36.png](https://community.atlassian.com/t5/image/serverpage/image-id/329480iE83CBEFAE04AA682/image-size/large?v=v2&px=999 "2024-06-12 15-36.png")


author: Trudy Claspill
body: [@Marie-H?l?ne PARISATO](/t5/user/viewprofilepage/user-id/4508655)

Si vous souhaitez que les t?ches soient clon?es lorsque l'utilisateur le souhaite plut?t que automatiquement, vous pouvez utiliser un d?clencheur manuel pour la r?gle d'automatisation.

<https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Manual-trigger-from-issue>

----

If you want the tasks to be cloned when the user chooses rather than automatically, then you can use a Manual trigger for the Automation rule.

<https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Manual-trigger-from-issue>

comments: author: Marie-H?l?ne PARISATO
body: i want to create a rule that clone my task in multiple task avery month or week.

Like if a had create a recurrent task on day or month or week ;

![tache recurrente teams calendrier.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/328641iABFAC3294E28906E/image-size/large?v=v2&px=999 "tache recurrente teams calendrier.PNG")![tache recurrente teams.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/328640i21955A77DDBC216E/image-size/large?v=v2&px=999 "tache recurrente teams.PNG")


author: Trudy Claspill
body: Bonjour Marie-H?l?ne,

Si vous souhaitez que les t?ches soient automatiquement clon?es chaque mois ou chaque semaine, vous devez utiliser une r?gle avec un d?clencheur de planification. Pourquoi pensez-vous que cela ne fonctionnerait pas pour vous ?

Les images d'?cran que vous avez fournies ne semblent pas provenir de la fonctionnalit? native du produit Atlassian Jira. Pouvez-vous nous dire d'o? viennent ces probl?mes ?

N'h?sitez pas ? publier votre r?ponse dans votre langue maternelle et nous utiliserons des applications de traduction pour la convertir dans nos propres langues si n?cessaire.

-----

Hello Marie-Helene,

If you want the tasks cloned every month or week automatically then you should use a rule with a Schedule trigger. Why do you think that would not work for you?

The screen images that you provided do not appear to be from the Atlassian Jira product's native functionality. Can you tell us where those issues come from?

Please feel free to post your response in your native language and we will use translation applications to convert it to our own languages when needed.


author: Marie-H?l?ne PARISATO
body: i'm working to a transition between teams and JWM.   
Picture are from TEAMS. And user used to create recurrent task.  

i will work after to a transition between TRELLO ad JWM. Hope it's will be easier.


author: Marie-H?l?ne PARISATO
body: users want to see all the recurrent task created just after they create the first task. that why the scheduler won't do the job. because the scheduler will do that the rule will be scheduled and will create every month only one task.


author: Trudy Claspill
body: The user will not be able to see recurring tasks that have not yet actually been created. The calendar features in Jira will show only tasks that actually exist.

Instead of running the automation on a monthly or weekly basis to create the next immediate instance of the recurring tasks, you would need to run a rule that would create the recurrent tasks in bulk now, setting the dates on them for the appropriate future dates when they need to occur.

For instance, for tasks that recur daily you could have a rule that runs monthly and creates a new task for each day in a future month. For tasks that occur weekly you could do the same thing.

Or you could create a manually triggered task that would do the same thing.

In that manner you could pre-load your recurring tasks for the next month or several weeks.


author: John Funk
body: Hi Marie-H?l?ne,

See if this article helps you:

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

comments: author: Marie-H?l?ne PARISATO
body: it's not for me because it's a recurrente rule that work every week for example and create a task . And i want a rule taht create a task for each week until ever.


author: John Funk
body: So what you are saying is that the tasks must be created in advanced - before the current one is completed.


author: Marie-H?l?ne PARISATO
body: yes, sure, in order for the manager to be able of have an idea of occupation of his teams member on the futur day/week/month...


author: John Funk
body: You could probably create some type of automation rule that creates the issues until a certain date. It would be sort of self looping that would fire and then stop when it creates an issue with a certain Due Date. You would kick it off and then watch it until it is done and then turn the rule off. I would run it after hours though just to not interfere with other work going on.


author: Marie-H?l?ne PARISATO
body: ok, i will think about it. thanks