Sounds simple but.....
They have a bunch of other issues to be auto-created, but the conditions are similar so no need to list them all.
CALLOUT! This is in a team-managed project, but I think the same logic may apply to company-managed. I have no experience in team-managed projects.
I am not sure how to set the date logic.
Thanks in advance!
Hi @Gail
How far did you get? Where exactly are you struggling? Could you show a screenshot of your rule and show us where exactly (date logic) the problems are?
Best
Stefan
Hi Stefan. Honestly I did not get far. I'm hung up on how to do the following:
On the new subtasks created from trigger issue (...when new issue type Webinar is created) I have no idea how to set the new subtask start date and due date based on its parent. I think it requires branching, but I'm pretty sure my last steps in the screenshot are wrong.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Gail
As far as I got your requirement right the rule in the attached screenshot should deliver the expected result:
Please let me know if this works and was helpful.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome! You‘re welcome ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you reviewed the documentation on using Smart Values for the trigger issue to set values in the issue being created by the automation?
https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.