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: Create child issue (task) on Epic when specific field is entered > More context below

Breanna Williams

- When custom field in epic is selected as "yes", I would like for it to auto-create a child issue titled "xyz". I am seeing that this is is possible for sub tasks but I need this to be a task level due to the hierarchy in the future advanced road map

- There will be multiple child issue / custom field connections but I believe the same if/then/action can be duplicated once I get the shell down.

- Please see attached image with how far I have gotten

Screen Shot 2023-04-20 at 2.37.29 PM.png

Accepted answers

All comments

Trudy P Claspill

Hello @Breanna Williams

Is this for issues in a Company Managed project or a Team Managed project?

With the way you have the rule set up it is triggered when a new issue is created, and then the For Epic branch is looking for the parent Epic of the issue just created.

I don't think that is the scenario you described.

It sounds like maybe it is the Epic itself that is being created and should be triggering the rule. Is that correct?

If so, then in that case you would want to remove that For Epic branch and instead

1. Have a condition to check if the newly created issue is an Epic

2. Have a Condition > If/Else Block to check if the custom field is set to the value that indicates a child issue should be created, and create the issue under that If block

3. Follow with Else-if blocks for checking the other fields and creating other issues, if the checks are mutually exclusive.

Screen Shot 2023-04-20 at 11.53.55 AM.png

For a Company Managed project as part of creating the Task you would set the Epic Link field to {{triggerIssue.key}} to link the new issue as a child issue of the Epic where the field was changed.

Breanna Williams

Hi Trudy,

Apologies, I am new to Jira and should've mentioned this is for a Company-managed project.

Thank you for helping me with this breakdown -- you are correct. I would want the creation of the Epic to trigger this rule.

Rule should be:

- If "Yes, need to order" in custom field "Is product needed?" is selected, THEN a child issue should be created titled "Order Product For"

I am a bit confused on where the action is with creating the actual child issue? Could you explain more?

For additional context, the other custom fields I plan to use do not block one another. It is mainly to create a "to do list" based on the criteria added in the Epic. Let me know if that makes sense? @Trudy P Claspill

Appreciate your help thus far!

Breanna Williams

Screen Shot 2023-04-20 at 6.12.05 PM.png

Breanna Williams

A new screenshot ^ @Trudy P Claspill I'm not sure I did this last step correctly.

Elif Alverson_voegli

@Trudy P Claspill , I am working on a very similar automation. I would like to create child tasks based on the couple of fields. It does not create any tasks at all. It is a company managed project. Any suggestions? Thank you.

Screenshot 2023-06-16 at 6.08.46 PM.png

Trudy P Claspill

Hello @Elif Alverson

If your situation is "similar" but not identical, please start a new Question and provide the details of your scenario. That way, if we provide a working solution for your scenario the post can be marked as Answer Accepted and be found by other users with similar questions.

Include the information from the Audit Log showing the details of the rule execution.

Elif Alverson_voegli

@Trudy P Claspill , thank you for your response. I will start a new discussion.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

atl-gruland