Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Automation rule for Status sync for Feature and epic (child issue)

Hello Community,

I was following this thread below:

Solved: Automation for Moving Epics to In Progress/Done wh... (

But I am looking for a different solution.

I am looking for a jira automation rule which when enabled to sync the feature with the epics (child issues). Whenever the epics goes into 'In Progress' status, the feature status should be updated to 'In Progress' as well.

1 answer

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 17, 2023


For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Features are not in the built-in issue hierarchy, and so I hypothesize you have added them.  In that case, you may need to use JQL to branch to the parent, such as with:

  • trigger: issue transitioned
  • condition: issue type equals Epic
  • branch: on JQL of key = {{triggerIssue.parent}} AND issueType = "Feature"
    • condition: add any additional conditions needed
    • action: transition the issue

As you are doing this, please consider the case of the Feature has multiple children Epics: what should happen to transitioning the Feature for differences in child Epic status values?

Kind regards,

Suggest an answer

Log in or Sign up to answer