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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am using Lookup Issues in automation to count the number of child issues. For most of the Epics, this is working but I noticed that when we have a child issues that happens to belong to another project, it does not include it although it has the correct Epic name which I am using for the search.
Here is the query I use in my rule:
issuetype in (Bug, "Client Story", "Non-Quattro Bug", "Non-Quattro Story", Story, Task) AND "Epic Link" = "{{issue.Epic Name}}" and Status in("Warranty", "Done")
And here are the child issues it is finding.
And here is the same query in my filter with the child issues found.
Here is a screenshot of the Epic. As you can see, CS2-84 is a child issue of CS-126 so why wouldn't my automation recognize it?
hi @Colleen Gotling ,
I have not attempt this myself. The first thing that comes to mind is whether the automation is global or not? I would think that it would either have to be global or at least a multi project automation. Do you likely have already thought of this but wanted to throw it out there.
Thank you for replying but I think I found my issue. It is a global rule with multiple projects but the CS2 project I forgot to include. Now it works.
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.