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.
My requirement is, I would like to automate parent issue transition when 2 or more sub-tasks of that parent issue are in a certain status.
Example: If parent issue is in open status, and when two or more of its sub-tasks are changed to "status A", then parent issue should be moved to in-progress.
For this, I have used advanced compare condition in automation for jira.When this condition is met, For parent, status transition to happen.
But when I tested this automation rule, even when there is one sub-task with statusA, the automatic transition is happening. It is considering the condition "greater than".
I would like to know if it is possible using automation for jira plugin, if so, what should I make changes in my approach.
Thanks in advance.
Hi @Sarath
It seems your advanced compare is only testing the one sub-task and not the others.
Have you considered using JQL and Lookup Issues to find the sub-tasks which are in the status you care about, and then check the size to see if there is more than one: {{lookupIssues.size}}
If more than one, then update the parent.
Best regards,
Bill
Thank you, we're using automation for jira in server version. Seems like lookup issues action is not available in this moment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, Sarath.
That is correct that Lookup Issues is only for cloud version. For server version, JQL result sets are representented by the {{issues}} smart value (note this is plural). So then {{issues.size}} could work for you.
https://confluence.atlassian.com/automation/smart-values-993924860.html
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.