How can I make reccuring Epic with its task

[Lazo Dana Shawkat]

Hello Dears 

I have been assigned to create an epic with its tasks that have specific due dates, the requirement is to make this epic and its task to reccur or repeat every month meaning being created every month but with the same date but only diffrent month, the rquirement is to do it using jira automation, I am seeking for your kind help I looked every where and I couldnt implement it 

[Valerie Knapp]

Hi @Lazo Dana Shawkat , welcome to the Atlassian Community and thanks for your post.

I would use a rule like this one - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180 , as a basis to start from.

Basically, you are saying you want a scheduled rule to run, let's say, on the first day of the month to create an Epic and some child Tasks.

You would just need to change the trigger here 

Please make a test rule and see if you can get it working. Let us know if you need more help.

Best wishes

[Trudy Claspill]

Hello @Lazo Dana Shawkat 

You mentioned that the tasks have "specific due dates". How are the due dates determined each month? For example, are they relative to the beginning of the month so that one task is due on the 7th day and another on the 13th day?

As @Valerie Knapp you could set up an Automation rule triggered on a Schedule and have it create the Epic and the child issues.

Start with a Scheduled trigger.

Add a Create Work Item step to create the Epic.

Use a Related Issue branch to change the focus of the rule to the newly created Epic.

Within the branch add a Create Work Item step for each Task you need to create.

In each of those steps set the Parent field for the Task to Current Work Item. That will make the Epic the parent of the Task.

You can set many fields when you are creating a work item by selecting the field from the Choose fields to set list and then specifying the value.

When you provide more information on how you would want the Due dates for the Tasks set, we can offer you more advice.

[Lazo Dana Shawkat]

---

Hello @Trudy Claspill Dear,

I hope you're doing well. Thank you so much for your previous response it was very helpful and truly appreciated.

I’d like to clarify my original question, as I realize now I may not have explained it clearly enough.

We have an epic titled "End Month List", which currently contains around 67 tasks. Each of these tasks has:

A unique summary/title

A specific assignee and reporter

A detailed description

A defined due date, such as 07/16/2025, 

Our goal is to automatically recreate this entire epic every month, maintaining:

The same structure (same titles, descriptions, assignees, reporters)

But only updating the due dates so that they fall on the same day of the month, but in the next month (e.g., a task due on 07/16/2025 would become 08/16/2025 in the recreated epic).

We would like this recurring epic creation to be triggered automatically on the 15th of every month (e.g., the August epic would be created on 08/15/2025).

[Lazo Dana Shawkat]

Just another note I forgot to mention that all the tasks have specific due dates as I mentioned not only the epic we want to change but the tasks due dates as well like if a task has a due date if 7/20/2025 it will be created with the same assignee and everything but only changing it to 8/20/2025 this has to be done to all 67 tasks due dates 

[Trudy Claspill]

Hello @Lazo Dana Shawkat 

Thank you for that clarification. That is very helpful.

You said you want this triggered on the same day each month; the 15th.

When the rule runs on August 15, would the due dates be set for dates in August or dates in September?

Since the Epic has 67 children and rules are limited to 65 components, you won't be able to use my previous suggestion.

I have links to other post that provide details for copying an Epic and all it's children in my other computer. I will post those tomorrow as it is now 10:30 pm where I am.

[Lazo Dana Shawkat]

Hello @Trudy Claspill 

Dear thank you for your support its truly appreciated, and yes the due date should be set to August so if we are now in July when the new epics and tasks are generated again it should be in August so exactly for next month. I am very grateful that you have taken time to answer this comment even when the time is late from your side.

[Trudy Claspill]

Hello @Lazo Dana Shawkat 

This article talks about a rule to clone an Epic and its child issues, plus a second rule to clone subtasks of the child issues.

https://community.atlassian.com/forums/Jira-articles/Clone-Epic-Stories-and-Subtasks-tree-with-Jira-Automation/ba-p/2316387

This Question talks about cloning just the Epic and child issues. Note that this is an older post and mentions the use of the "Epic Link" field. That field has been deprecated and the "Parent" field should be used instead.

https://community.atlassian.com/forums/Jira-questions/Clone-EPIC-amp-Stories-to-New-Epic-and-link-New-Stories-via/qaq-p/2257134

In both of these example they are using a manual trigger, where a user would first navigate to the Epic and then manually trigger the rule. In your case you want to use a Scheduled trigger with a JQL that will select the Epic to be cloned.

In the JQL above replace YourEpicKey with the key of the Epic you want to clone.

Make sure that you uncheck the box below the JQL statement where it says "Only include..."

The other difference is your requirement to set the Due date based on the original issue Due date. I'll explain that in the next step where the new Epic is created.

Create the new Epic

Next you would use the Clone action to clone that Epic. In the Epic you would need to set a new Due Date based on the day of month in the original Epic. Here is the step, and I will follow that with an explanation of the smart value I used for the Due date.

{{now.endOfMonth.plusDays(issue.duedate.format("d").asNumber).jiraDate}}

"now" says to start with the current date/time.

Adding .endOfMonth says shift to the last day of the current month.

Adding .plusDays says add a number of days to the last day of the month. The number of days to add is specified in the parentheses.

I'm going to skip over the days to add portion for a moment and come back to it.

Adding .jiraDate says to format the data as a the default format used in Jira Date fields.

Coming back to the "days to add" portion:

issue.duedate says to get the Due date field value from the issue currently in context, which is the Epic selected by the rule trigger.

Adding .format("d") to it says get the day of month from that date.

Adding .asNumber to it says treat the result as a number.

So, let us say that the original Epic Due date is 7/7/2025, and this rule runs on the 15th of July.

issue.duedate.format("d").asNumber will get the value 7.

now.endOfMonth will get the date 7/31/2025 (plus the current time)

.plusDays will add 7 to that date/time giving us 8/7/2025 plus the current time.

.jiraDate will reduce that value to just 8/7/2025, in the format used for Jira Date fields.

Note that some fields in the Epic may not be automatically cloned into the new Epic. After running a test of this rule examine the new Epic to see if all the data you need was copied. If not, in the above step you will need to explicitly select the fields that need to be set and copy the values from the "Current work item"

You can use that same logic within the Branch that clones the child issues of the original Epic, to set the Due date for each newly created child issue.

Let me know if that is enough information for you to develop your solution, or if you have more questions.

[Lazo Dana Shawkat]

Hello @Trudy Claspill 

First, I would like to thank you for this explanation I understood everything, and it was pretty clear. But I still can't manage to create this recurring epic and its tasks, do you have any suggestions for me 

[Trudy Claspill]

Hello @Lazo Dana Shawkat 

Please provide screen images showing us the entire rule you have created.

When you say you can't manage to create the recurring epic and tasks, what do you mean exactly? Is the rule executing? Are you not getting Epics and Tasks created? What do you get? 

If the rule is executing and you are not getting the results that you expect, please share with us the details from the Audit Log for when the rule executed. Make sure the click on all the ">" characters to the right within the log entry to expose all the details of the entries.

[Calvin]

Heya, not sure if its helpful, but there is new functionality incoming (or maybe already in) that can help create recurring items as well

https://support.atlassian.com/cloud-automation/docs/automatically-clone-an-issue-when-done/

[Lazo Dana Shawkat]

Hello @Calvin 

I hope you're doing well. Thank you so much for your previous response it was very helpful and truly appreciated.

I’d like to clarify my original question, as I realize now I may not have explained it clearly enough.

We have an epic titled "End Month List", which currently contains around 67 tasks. Each of these tasks has:

A unique summary/title

A specific assignee and reporter

A detailed description

A defined due date, such as 07/16/2025, 

Our goal is to automatically recreate this entire epic every month, maintaining:

The same structure (same titles, descriptions, assignees, reporters)

But only updating the due dates so that they fall on the same day of the month, but in the next month (e.g., a task due on 07/16/2025 would become 08/16/2025 in the recreated epic).

We would like this recurring epic creation to be triggered automatically on the 15th of every month (e.g., the August epic would be created on 08/15/2025).