Is it possible to create an automation rule for a subtask based on the parent epics or tasks?

[Lina]

At our company an epic is created for each project. a task is created for each booked medium of the project. and each medium has different sub-tasks. these are created automatically.

EPIC: Example 1 

Task: Example 1 | Facebook

Subtask: Task: Example 1 | Facebook | To-Do

These sub-tasks should automatically receive a start and due date, based on the set start and due date of the medium. 

For example, if I fill in a start date in a medium, the start date in the subtask should automatically be -3 days. 

I hope this is understandable. 

[Tessa Tuteleers]

Hi @Lina , 

If i read it correct you already create the subtasks using automation for Jira?

If so you can add extra fields to populate when creating the subtask, choose duedate and add something like 

{{triggerIssue.duedate.plusDays(3)}}

You can find more info about date-related smart values here. 

Hope this helps! 

- Tessa

[Bill Sheboy]

Hi @Lina 

Yes, and...to what Tessa suggests:

Do the start and due dates of your mediums (e.g. Facebook) ever change?  If so, you may need additional rules to detect this and update the subtasks which have not yet completed.

Kind regards,
Bill

[Lina]

Hey @Bill Sheboy @Tessa Tuteleers 

Thanks for the answer.

Exactly, we are already using automation to create the subtasks. However, this smart value doesn't work and I don't know why.

Normally, the start date does not change afterwards, it is set once and then the data should also be set automatically in the subtasks.

Which smart value do I use for the start date? 

{{triggerIssue.startdate.plusDays(3)}}

? 

 

Kind regards,

Lina 

[Tessa Tuteleers]

Hi @Lina , 

what is the original start date field? 
if it is a custom field, you can use both the name, or (in my opinion better) the custom field id like this: 

{{issue.MyDateFieldName}} or {{issue.customfield_12356}}

You can get the id by going to the custom field configuration and checking the id in the url. 

Hope this helps!

Tessa

[Bill Sheboy]

Yes, and...

Smart values are not consistent between the UX and their spacing/capitalization.  And sometimes you must use the custom field id value.  You can always learn what automation is expecting for the smart value by finding an example Jira issue with your data, and then trying this how-to: 

https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/