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

Change Epic status based on some or all linked issues statuses are updated to certain stage?

I want to change the status of an Epic when the status of one or all of its linked issues changes. The linked issues maybe on other projects and they can be tasks, incidents, bugs or sub-tasks.

The Epics I want to automate are on "Operation" project. I don't want this rule to execute on "APP" o "Web Crawling" projects.

(1) An Epic must be on "To do" that has linked issues from the same project and also from other projects, that are also on the backlog in the "To Do" status. As soon as one of his linked issues transitions from the backlog to an "in progress" state, I'd like to update the status of the Epic to "in progress" status as well.

(2) The Epic would then stay in a status of "in progress" until its last linked issue move to the state of "done", then the Epic will move into state of "done".

I have several Epics so it is ideal to automate so we never have to actually change the statuses of our Epics.

Thanks for the help.


This is my current workflow but it is not working

Captura de pantalla 2017-10-15 a la(s) 11.51.27.png

3 answers

2 accepted

0 votes
Answer accepted

Thanks @Mark Chaimungkalanont that worked great!!

Well done.



i have a similar problem, could you please post your complte rule configuration?

Thank you!



fixed it!

We do not use stories in our workflow...


Like Michael Turcato likes this
0 votes
Answer accepted

Hey there Sebastian,

In Jira, Epic links aren't "normal" issue links so that's why your "linked issue match" doesn't match anything.
You'll need to use the "JQL issues" drop down and enter:

"Epic Link" = {{issue.key}}

as the "Related issues JQL", before entering the appropriate statuses. (see image below)

Hope that helps!



Mark C



Hi Mike @Sebastian , I'm having exactly the same problem . but couldn't figure out the solution you proposed .should I first install a plugin ? can you please help me as well ? 

Hi @NEGAR JALALIAN  sure happy to help.

You should install Automation for Jira plug-in first. {from code barell}.

Then I can help you configuring an automation rule is very graphic, easy and user-no programmer-friendly.


Like NEGAR JALALIAN likes this

@Sebastián Delmastro  I have now installed the plugin . will you please help me ?

all I need to do , I want to map status of Epic with the status of tasks and stories which are linked to the mentioned Epic .  

HI All,

my requirement is to match child issue status with "Epic status " is it possible? If Yes , Please share the rule.

My criteria is to create 

epic statuses to be updated automatically reflecting the status of its children issues, so there will be no need for manual updates of issues  that appear as cards on the boards.
Acceptance Criteria
1 When the first task is moved from (Backlog ot open ) to ( In review, in progress, test) or ( Closed with resolution Done)
 then the epic moves to inprogress
 And "EPIC status move to inprogress.

I tried my best to achieve this rule by using related issue condition and issue condition .JQL . but I am not able to success this rule.

Please help me to get it solved.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events