Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Clone the parent task in 30 days when a particular sub task has been completed

Craig Booth December 14, 2018
I have a task that’s been created with 6 sub tasks. This is to control a licensed product for our customer that needs various forms of customer contact through out. However let’s say I reach task 4, I then would like Jira to recreate this parent task (including sub tasks) in 30 days time but the trigger has to be this particular sub task as this determines the 30 day count down of the next customer engagement. This could be different times each month as it depends when this task is completed and when the customer comes back to us. Is this possible to automate this? I have the automation plugin and repeating issues plugin however it’s the 30 day task creation delay based on a sub task completion I am struggling with. Thanks

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 17, 2018

Hello Craig,

Thank you for raising this question.

After trying some options using Automation for JIRA, I was able to achieve the functionality you were looking for by performing the following steps/requirements:

- Create a date custom field and add it to your project screens

- When starting the progress on The sub-task 4, you must require the user that did it to fill the created field 30 days ahead of the current date

- Configure the automation rules like the below:

 

Screen Shot 2018-12-17 at 16.47.14.png

P.S: I used the Due Date field to trigger the last automation rule.

Please, let me know if it makes sense to you.

Craig Booth December 18, 2018

Thanks so much for looking into this,  However what is the custom field called you have used as I cannot see it in your query? 

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 18, 2018

Hey Craig,

I used the Due date field to trigger the automation. In fact, you can use any date field to do it, I've only suggested a new date custom field to avoid confusion with your users since this field will be used only to trigger the automation and nothing else.

In fact, I've found a better option to achieve this feature. Here are the exact steps I performed:

- Add a date field to your project screens

- When starting the progress on The sub-task 4, you must require the user that did it to fill the date field 30 days ahead of the current date.

- Create a rule that will check once in a day if the date field was reached (With the query below) and Clone the parent issue of the sub-task which breached the date.

datefield >= StartOfDay() and datefield < endOfDay()

Screen Shot 2018-12-18 at 11.32.23.png

Please, let me know if this makes sense to you.

Craig Booth December 19, 2018

Is this the whole process?  When I see this via email I see another part of the automation (see below)  Could you send me the complete process please?

To add in for automation.PNG

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 19, 2018

Hello Craig,

As mentioned in my last message, I've found another option to achieve this matter, better than the one sent before.

I realize that the automation I mentioned in my first answer is not required to achieve the functionality you are looking for.

That been said, please let me know if the steps I provided in my last message works for you. :)

Craig Booth December 19, 2018

I had to tweak it slightly as using <end of day wasn't bringing back any results and I changed the schedule to 5 minutes to test. However I get the following error.Automation Error.PNG

Using the below automation works however the sub task doesn't get created!  Any thoughts in why this would be?

 

Automation Working.PNG

Suggest an answer

Log in or Sign up to answer