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

Adding subtasks to an epic upon its transition

Osama Al-Areky

Hello,

I would like to automate the addition of new sub tasks to an epic once this epic is transitioned, for example: an epic is transitioned from to do, to on going, then auomatically subtasks are created and added to it.

I tried different ways to create a rule, but it only creates new tasks outside of the epic, and when i try to create subtasks it doesn't allow me to add it to the epic, it gives error and it says that it has no parent in the hierarchy, althought i select to apply to the current issue.

Accepted answers

Trudy P Claspill

Hello @Osama Al-Areky

Welcome to the Atlassian community.

Are you working with epics in a Team Managed project or a Company Managed project?

The issue type Sub-task (or Subtask) is not intended to be created under an Epic. The issue hierarchy is:

Epics
|-- standard level issue types - i.e. Story, Task, Bug
    |-- subtask level issue types

So, the automation rule will not support you creating a subtask attached directly to an Epic.

Can you provide more information about why you are trying to create subtasks attached directly to an Epic?

All comments

Trudy P Claspill

Hello @Osama Al-Areky

Welcome to the Atlassian community.

Are you working with epics in a Team Managed project or a Company Managed project?

The issue type Sub-task (or Subtask) is not intended to be created under an Epic. The issue hierarchy is:

Epics
|-- standard level issue types - i.e. Story, Task, Bug
    |-- subtask level issue types

So, the automation rule will not support you creating a subtask attached directly to an Epic.

Can you provide more information about why you are trying to create subtasks attached directly to an Epic?

Osama Al-Areky

Thank you so much. It's sorry i meant adding tasks to an epic upon the transition of the epic. It is a team managed project.

Osama Al-Areky

Actually i tried both sub-tasks and tasks. just to see if it makes a difference. For the sub-tasks it gave me an error saying that it has no parent. For the task, there is no error, but it creates the issues outside of the Epic, and i couldn't find an action to add the issues to the Epic. There is a field that allows me to select where I want to apply the action, whether the current or the triggering issue, but both don't do anything.

Trudy P Claspill

You will have to use the More Options option to edit the Parent field of the new issue to set it to the issue key of the parent epic.

Screenshot 2023-10-19 at 4.35.28 PM.png

Thibaut Subra _Elements_

Hi @Osama Al-Areky

If you want to easily create child issues for your Epic, you can use our application Elements Copy & Sync.

From you Epic, you trigger a recipe that will create multiple issues (a static or a dynamic number) and you link these issues to your Epic with our is part of Epic link type.

Capture d’écran 2023-10-20 à 15.39.57.png

That way, you can create any type of issues under your Epic.

Capture d’écran 2023-10-20 à 15.42.15.png

Of course, you can use Jira Automation to trigger your recipe if needed.

I suggest trying our app, it's free during 30 days and remains free under 10 users.

Let me know if you need help with that!

Regards

Thibaut

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