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

Link Issue (Tasks with sub-tasks) to Epic in Jira Automation Rule

Natalia Golikova

Hi everyone,

I would like to create a monthly scheduled rule with Epic and Tasks which have Sub-tasks. How can I link Tasks (Issues) to the Epic?

If I create a branch it doesn't give me to add one more level a branch with subtasks for the recent created issue.

What are the options?

I found a similar question

https://community.atlassian.com/t5/Jira-questions/How-can-I-create-a-Epic-on-a-schedule-and-then-create-subsequent/qaq-p/759810

Thanks!

Accepted answers

Petter Gonçalves

Hello @Natalia Golikova

Thank you for reaching out.

Per your description, I understand that you want to schedule an automation rule to create a pre-configured number of Epic, Tasks and Sub-tasks (Linked to each other) at the start of the month. Is that correct?

To achieve that, you can configure three rules and, using a common field value, make each one to be triggered by the other in a waterfall basis, properly creating the related tasks and sub-tasks as you need.

These would be the exact steps to achieve your need:

Create a new select list custom field with the option "Automatically created", adding it to the create screen of your Epics and Tasks
Create a scheduled rule to create the Epic you need and set the Epic with the option "Automatically created" in the custom field you created:
Create another rule to create your tasks and link them to the Epic that triggered the rule. To do it, flag the rule to be triggered by another rule (In the Rule Details) and set it to trigger when an Epic is created with the custom field set as "Automatically created":
Create another Rule(s) with the same logic to create the sub-tasks:
P.S: If you want to create multiple tasks and Sub-tasks, you can add more options in the Custom field (Like task 1, task 2, etc) and use them to properly select which tasks the sub-tasks must be linked.

Let us know if this is what you are looking for or if you have any questions.

All comments

Petter Gonçalves

Hello @Natalia Golikova

Thank you for reaching out.

These would be the exact steps to achieve your need:

Create a new select list custom field with the option "Automatically created", adding it to the create screen of your Epics and Tasks
Create a scheduled rule to create the Epic you need and set the Epic with the option "Automatically created" in the custom field you created:
Create another rule to create your tasks and link them to the Epic that triggered the rule. To do it, flag the rule to be triggered by another rule (In the Rule Details) and set it to trigger when an Epic is created with the custom field set as "Automatically created":
Create another Rule(s) with the same logic to create the sub-tasks:
P.S: If you want to create multiple tasks and Sub-tasks, you can add more options in the Custom field (Like task 1, task 2, etc) and use them to properly select which tasks the sub-tasks must be linked.

Let us know if this is what you are looking for or if you have any questions.

Natalia Golikova

@Petter Gonçalves Thanks a lot! It works!

Michael Trice

Does this work for Next Gen projects?

Dr Sudhir Ajja

@Petter Gonçalves I did and rechecked everything, but ...

on autorun,
1. the epic (patient name) gets formed
2. Task (e2) gets formed, but NOT IN THE EPIC
3. Subtask gets formed, in the task
If I manually create new Epic
1. epic is formed> task inside it> subtask inside it.

Can anyone tell me where am I going wrong?

Link for all images.

Petter Gonçalves

Hello @Michael Trice and @Dr Sudhir Ajja

The steps above are only applicable to Classic projects, so it might not work for Next-gen projects.

For Next-gen, you must use the Parent field instead of Epic link to link both Epic and task.

Let us know if this information helps.

jorma nordlin

Does the automatically created task make trigger at all? I tested this. I thought maybe this wouldn't work. I did a simple test. The first automation created a task. Second automation triggered when first task is created and created another task if task's reporter is Automation for Jira. This didn't work.

Maybe when creating a task, the trigger only works if we using the user interface. I don't know.

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

automation