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 the name of Epic into Sub-tasks Summaries

Hanieh Katebian

Hello everyone,

I have been searching for an automation rule which would help me to have the name of Epic and paret ticket shown in the titel for the sub-tasks. I found a previous answer in the discussion but they trigerred only one Sun-task.

I am responsible for projects which have the same steps to go through. Each project is an Epic for me and each Task is a big step. Inside some Tasks, I want to define clear smaller steps for my team to go through. The proble with Sub-tasks is that as my team receive the notification, they won't be able to see the Epic name unless they go one level back. So, what I need is to create a new task, and have 7 Sub-tasks created automatically and each one of their summaries include the name of the Epic and the parent PLUS their own specific name. I tried to use the smart values for the Summary, but it doesn't work. I attach a screenshot with the hope that it might help you understand my question.

The values I used for my sub tasks are:
{{issue.parent.epic.summary}} {{issue.parent.summary}} Task 1

{{issue.parent.epic.summary}} {{issue.parent.summary}} Task 2

{{issue.parent.epic.summary}} {{issue.parent.summary}} Task 3

I aprreciate your help with that. Thanks!

Accepted answers

Gaurav_0av1h6

Hello @Hanieh Katebian

As the automation for sub-task is triggered when a Task is created, it considers the Task as the issue. Hence, when we say, {{issue.parent.epic.summary}}, the automation is unable to understand as the Task has Epic as the parent.

Update the automation with '{{issue.epic.summary}} : {{issue.summary}} : Task-1'. It is working as expected for me.

Please accept the answer if this helps solve your query else respond and allow others to share input.

All comments

Gaurav_0av1h6

Hello @Hanieh Katebian

Update the automation with '{{issue.epic.summary}} : {{issue.summary}} : Task-1'. It is working as expected for me.

Please accept the answer if this helps solve your query else respond and allow others to share input.

Hanieh Katebian

Hello @Gaurav ,

thanks for the fast answer, I tried your suggestion and it works for the {{issue.summary}}, but the {{issue.epic.summary}} is still not showing which is even more important that the Taks name for me. Let me explain further, maybe it helps. I have already a Demo Epic with a task "WMBCreation" ready. Whenever I have a project, I Clone this Epic with its children and Name the new Epic as the new project and click create. The new Epic, with the Task and its sub-tasks are created but in the Summary of the tasks, only the Task name is showing.

Am I missing something in between?

Gaurav_0av1h6

Hello @Hanieh Katebian

The native Jira functionality does not allow the child tasks to be cloned with the Epic. Are you using an add-on to clone the child tasks with the Epic? It could be one of the reasons that automation is not behaving the way it should.

If you are creating the Epic in the same Jira project, then I would suggest creating automation for creating Tasks as well, the same way it is done for Sub-Tasks.

Hanieh Katebian

Hello @Gaurav ,

yes you are right. I am using the add-on because unfortunately, it is not possible to automatically assign tasks to an Epic whenever a new one is created. I have been looking for a solution because all the steps in the projects are the same and I just needed to create a new Project (Epic) and all the tasks and sub-tasks could be automatically added. The only issue is that in Nex-gen projects, I can't add the epic automatically to the tasks. Therefore I decided for the add-on. You suggestion would be perfect if I could automatically connect the Task to the created epic.

Shane Kelly_dcjljz

I use the dynamic variable capabilities of the Template App.

Dynamic variables - Issue Templates for Jira (deviniti.com)

Just add

[variable name]*

anywhere in the template. When you create issues based on this template, you will be automatically asked to enter a name for the variable.

We constantly use this feature. This app is just plain awesome.

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