How to automate - based on a real life date (not date in a jira item)
Asked by Steve Gardner:

Hi,

looking for a way to do the following.. open to any/all solutions.

Lets say i have an epic (or maybe even a project)- with a random number of stories / tasks (and realtes subtasks for both)....

On a specific real life date (ie first of each and every month) - i want to automate cloning all items in that epic (or project) and move them to our main project's backlog.

I.e. imaging im dealing with lawn care...

so i have 5-10 sotories realted to mowing lawn, weeding, edging, etc.. and each month i want those items to be "March- Mow lawn", "March- Weed Lawn", "March - edge lawn" , etc. then on April 1st, the april to do list is created....

thoughts on how to get this created? or do i need to create 12 holding items - (Jan-Dec) items that have due date on the 1st of the month and have them be triggers?

thanks in advance,

Steve


Answers:
author: Steve Gardner
body: Thanks.. some follow up questions.. how do i at the appropriate scheduled time - clone everything that is part of an epic...

i think your solution is somewhat different.. in that at a specific time - it adds new items to an epic...

im trying to take the 5 items that are already assigned to the epic (ie parent= ParentID) and clone those 5 items and their sub tasks...


author: shib saha
body: Hi [@Steve Gardner](/t5/user/viewprofilepage/user-id/3797107) , Yes this is possible, you need to use the Scheduled trigger where you can mention to run the rule on first day of month.

If you want to use the same epic for all the months, use the jql condition and use the jql 'key = Epic key', this will limit the automation to create all the task or stories within the same epic.

In action, use 'create Issue' and use branching for multiple task or story creation.

This way you can achieve the automated way of creating the child issue every month with defined fields data.

Please let me know if you have any query. Thanks

comments: author: Steve Gardner
body: greatly appreciate that info.. is there aready a sample automation either specifcally like this ,or similiar that i can see in action?


author: shib saha
body: Hi [@Steve Gardner](/t5/user/viewprofilepage/user-id/3797107) , I am sharing the automation rule i have created in my test environment for creating two task everyday with Summary field value only and it is getting created under the existing epic.

![Screenshot 2024-08-01 at 12.09.36?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339222i5EA0A4154631AFB3/image-size/large?v=v2&px=999 "Screenshot 2024-08-01 at 12.09.36?AM.png")

![Screenshot 2024-08-01 at 12.09.51?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339223i924F683D7BD80B18/image-size/large?v=v2&px=999 "Screenshot 2024-08-01 at 12.09.51?AM.png")

The setting for 2nd task will be same only except the summary details and like wise you can create multiple task, story under same epic using the same automation rule based on the requirement.

Please have a look and see if you are able to replicate the same in your case and let me know if you need any further assistance with this?

Thanks!


author: Steve Gardner
body: I keep getting incompatible components error messages...

1) When schedule -

2) if Issue matches JQL Parent = EPICNUMBER

3) Branch

3A) For Current issue

3B) Then Clone issue into same project


author: Steve Gardner
body: Thanks for your above - let me try to replicate it .. i had posted my attempt prior to seeing your how to.


author: Steve Gardner
body: here is waht im trying as an outline.. (could be completely wrong)


author: Steve Gardner
body: ![Jira Issue.png](https://community.atlassian.com/t5/image/serverpage/image-id/339229i5236E0706121F6DA/image-size/large?v=v2&px=999 "Jira Issue.png")


author: Steve Gardner
body: And then when i set the logic up to not use a branch the way thi woudl intuative thinkn about it...it gives me the same type of error - Incompatible componenets...

1) When Scheduled

2) if issue matchs JQL (Parent = ParentID) - exact code is Parent=GARDNER-79

3) then clone issue into current project...

why isnt it this simple?

![Error-79.png](https://community.atlassian.com/t5/image/serverpage/image-id/339230i88DDD687E2CB0B6A/image-size/large?v=v2&px=999 "Error-79.png")


Tags: cloud

jira-cloud