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 for Closed Epic with Open Child Tickets

Manipal Reddy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 11, 2023



I am trying to add a label using automation to issues where Epic is closed and still have Open tickets associated to it.

1. So far i have created a scheduled job, with a JQL Filter - Issuetype = Epic and status in ( Done, Closed)

2. Added a branch for stories and other issues in a Epic

  •  (New Component) Added JQL as Status != Done
  • Then Edit issue label and add a new label as "Closed Epic with Open Child Ticket"
  • Unchecked issues that have changed since the last time this rule executed

The Automation was not successful and it was not updating the label to open child tickets in the Epic.

Adding screenshot for reference.

2 answers

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.
Oct 11, 2023

Hi @Manipal Reddy -- Welcome to the Atlassian Community!

Your rule is close to what you need, although I expect it is currently adding the label to the child issues, and not the epic.

You could modify your rule slightly to use the Lookup Issues action to identify the child issues which are open, and then add the label.

For example...

  • trigger: scheduled with the same JQL you have
  • action: lookup issues, using JQL to find child issues which are open; please update the JQL to match your configuration
    • parent = {{triggerIssue.key}} AND issueType IN (Story, Task, Bug) AND statusCategory != Done
  • advanced compare condition: to check if there are any child issues meeting that criteria
    • first value: {{lookupIssues.size|0}}
    • condition: greater than
    • second value: 0
  • action: edit issue to add the label to the epic

Kind regards,

0 votes
Aaron Geister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 11, 2023

In the Schedule you can add the JQL there. That might help with the execution of the automation. If its not in there already.

I might make another recommendation here is to use the JQL for "resolution is EMPTY" rather then status or use: <statusCategory != Done AND resolution is EMPTY>

That should catch issue that do not have a resolution and are in the correct status. Please omit the <> that was just to show you the JQL.

Hope this helps. Please let me know I can make some screenshot if you aren't following.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events