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; } } }

Advanced Automation - Creation of a specific issue type triggers creation of related issues

Gail_8p6l1l

Sounds simple but.....

When issue type ABC is created manually THEN
- Create issue type DEF and make its start date 21 days before the parent issue's due date AND make its due date 14 days before the parent issue's due date

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!

Accepted answers

Stefan Salzl_0i980g

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

All comments

Trudy Claspill

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/

Stefan Salzl_0i980g

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

Gail_8p6l1l

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 Screen Shot 2022-06-17 at 8.57.57 AM.png

Gail_8p6l1l

Thanks Trudy. Yes I did view this but not sure how it applies when I'm using a parent and child issue. I use smart values all the time in JSM.

Stefan Salzl_0i980g

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

Gail_8p6l1l

Thanks Stefan - I will give it a try.

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

automation