Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Automation - Add Parent Epic

Is there some way that I can use Jira Automation to add a newly created task to an Epic?

Here's the scenario: Our team has agreed that all Task issue type items on their board will be associated with the same epic. I am trying to find a way to automatically add this epic to all items created with the issue type of Task. Can anyone help me with this?

2 answers

1 accepted

0 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 07, 2020

Hello @Reid Talbot

Thank you for reaching out and for the detailed explanation of what you are trying to achieve.

Can you please confirm if you are using a Next-gen or Classic project?

I'm afraid you can not do that kind of automation in Next-gen project yet (See AUT-1297), however, if you are using a classic project, you can follow the steps below to create an automation rule that will properly set all the newly created tasks to a specific Epic as soon as they are created in your project:

1 - Navigate to your Project > Project settings > Project Automation

2 - Create the following rule:

Screen Shot 2020-04-07 at 16.41.18.png

This is the rule background:

1 - The automation will be triggered when a new issue is created

2 - Using the Issue fields condition, the automation will check if the issue type of the new issue created is "Task" 

3 - Using the action Edit issue fields, the Epic link field of the issue will be edited, properly added with the specific Epic you want

Let us know if you have any questions.

We are on a Next-Gen project. So I'll just have to sit tight and hope enough people are concerned about this to get some traction.


Thanks for your help.

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 07, 2020

You are welcome, @Reid Talbot

You may know this information, but Atlassian has just acquired Code barrel, the organization behind the automation app we are talking about.

That being said, our next steps will be to improve the integration and functionality of this new app that is now part of the Jira Cloud application. Hopefully, we will be able to provide you with good about that soon. :)

Thank you for your understanding and have a nice day.

Like Jonas van Ravenstein likes this

Hi Petter, 

I am now trying to accomplish something similar as Reid was trying to do with Jira Automation (Cloud).

When Issue of Issuetype Epic is created, Then I create a new Story.  However using the Epic Link field to be set to the Parent (or in other words the Epic that triggers the automation rule) neither of the 4 options (Current, Parent, Epic or Trigger issue) puts the Story under the Epic that triggers the rule.

Should I use JSON instead or am I doing something wrong here? 



Screenshot 2021-02-11 at 12.00.52.png

Always good to have conversations with yourself, so this is one of them.

The project was created using the 'standard' project templates in Jira Cloud. In this case a Project Management template. The Issuetype Epic was added later to the Issuetype scheme.


When you add Epic to the Issuetype Scheme, you have to add the Fields Epic Name and Epic Link as well, because otherwise you can't use them. 

Epic Name was already in place in my situation, but after adding Epic Link as well all is working fine now.


I do want to state that it is somewhat counterintuitive to have to add the Epic fields manually, yet I also understand that automatic adding (by Jira application) of the fields could also lead to more complexities in the Cloud implementation.

Like Petter Gonçalves likes this

@Petter Gonçalves 

How did you add "TK-1" and "TK-2" to the list of epic links? 
I only have "Current issue", "Parent issue". "Epic issue" and "Trigger issue". 
Без названия (42).png

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events