You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello,
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
The Automation was not successful and it was not updating the label to open child tickets in the Epic.
Adding screenshot for reference.
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...
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.