nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

All comments

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

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

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.

Screen Shot 2023-03-09 at 8.48.45 AM.png

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud