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
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
In Jira Automation, I want to iterate through the results of a JQL query, then perform som actions on each item before going onto the next one.
I tried a POC using the Audit Log as my action and lookupIssues in a branch to use for looping (as I understand it). But it only acts on the first issue that is retrieved (there should be 11 issues in my test).
What am I doing wrong? This is my rule:
Hi @Cash Coyne
is there any output in rhe audit log? Could you share the audit log here too?
Could you add a log action before the branch just logging the lookupIssues to see if the lookup action returns the expected result.
Hi @Stefan Salzl , that helped, but not in the way you'd think. I investigated why I would get only one issue. Turns out, Jira Automation doesn't like filters that have actual names for assignees, not their ID. I have filters like:
assignee = ("Tom Jones","Mick Jagger","Taylor Swift")
And I had a Filter = "FilterName" in my JQL and that was only returning one issue. When I changed the names to the IDs, it worked. I also tested it by using email addresses instead of IDs and that worked to. It's just User Names it has a problem with. I prefer names to IDs as it's a heck of a lot easier to edit and update my filters!
So add that tidbit to your automation troubleshooting tips
Hi @Cash Coyne
The work-around for that account ID behavior of JQL is to use the IN operator and quotation marks. For example:
assignee IN ("user name 1", "user name 2", "user name 3")
That will leave the names as-is, without switching them to account ID values, for the search.