Automation: Ensure all subtasks of a story inherit the stories start date

[Nolan McConnell]

I've looked around the community and I've found a bunch of similar automation questions but I can't seem to get my exact issue solved. 

When a new hire story is created it has a start date on it. We build sub-tasks off of this story for action items. If the story start date is updated to a week later, I'd like for that to flow down to the sub-tasks. 

[Julien Peyrade _ Elements]

Hello @Nolan McConnell 

If you don't mind using an add-on, Elements Copy & Sync can help you do exactly this. It's free for Cloud instances up to 10 users and has a 30 days free trial for all.

I'm the Product Manager of the app, so I can help you if you have any question. Among many other things, it lets you create subtasks that can inherit any value (fields, attachments, comments, workflow statuses...) from their main task.

Those values can be synchronized if needed, so if your start date field is updated in your main hiring task, it will be automatically updated in all its subtasks as well.

I hope this helps.

Kind regards,

Julien

[Jens Schumacher - Released_so]

Hi @Nolan McConnell , 

Did you look through this answer? It seems to do exactly what you are after.

Cheers,
Jens

Released.so - Release notes powered by Jira

[Nolan McConnell]

Thanks for sharing this. I've looked through about 4 other similar issues that didn't work for me but I think this one will. Appreciate it!

[Nolan McConnell]

After following that article you sent me @Jens Schumacher I still can't get the expected result. I'm thinking because we have a custom issue type. Thoughts on how to execute for a issue type that is "IDM Automation"? Below is the setup I have following the article you shared.

[Jens Schumacher - Released_so]

Not sure why the issue type would matter in this case, as long as the fields are the same.

Did you try to see if it works with the regular issue types? Do you see any errors in the logs?

[Nolan McConnell]

I have not tried it with other issue types since this project is the only one using this field and custom issue type. Tried using the "copy from current field" in the edit issue field and it didn't work. 

[Jens Schumacher - Released_so]

Sorry @Nolan McConnell 

It's hard to give advise from the screenshot alone. There might be a bit of trial and error required to get this going. A couple things that come to mind, 

If I remember correctly from the linked Article, this only works for issues one level deep. So if you change an Epic, the start date for subtasks won't be adjusted.

The other thing I noticed in the screenshot is the "disabled" in the top right. Make sure the automation rule is "enabled" when you try it. This feels like "Is the power cable plugged in?" advice, but still worth pointing out. :) 

Cheers,
Jens

Released.so - Release notes powered by Jira