A4J - identify issues in the same version when status changes

[Dave Furlani]

We have a done status called Sprint Complete. What I'd like to do is to send a message to the test team when all Stories for development in same fix version are in a status of Sprint Complete. and ready to be built into a release. Those fix versions are usually set mid sprint, when the first Story is In Progress

Branching the rule on fix version or with JQL sounds like it should work, but are giving errors because my trigger is based on status change. 

I can get JQL to find:

• All the Stories with the same fix version as the trigger 
• All the Stories with the same fix version as the trigger in the status of Sprint Complete

If I can make the rule count the rows in those JQL statements and compare the counts, I can identify when all the Stories in the fix version are done and alert the test team to trigger a build.

Sadly I'm having trouble getting those counts because the rule branching for versions seems to only accept version release/change/create/delete as a compatible trigger. The trigger we want to use will be status change. I've also tried scheduled during my PoC.

Does anyone know a way to achieve the result I'm after?

[Trudy Claspill · Accepted solution]

Hello @Dave Furlani 

When asking for help with an Automation Rule it is important that you show us the rule you have constructed. Without that we are missing vital context and details necessary to offer you advice on changes to make.

Please show us the rule you have constructed.

[Dave Furlani]

Image added

[Trudy Claspill]

In your Schedule trigger are you using a JQL statement? If so, what is it?

[Dave Furlani]

I think I was using the same as the first branch JQL - the one highlighted in the image above.

I had the schedule running every 5 minutes and only running on tickets that had been changed since last execution

[Trudy Claspill]

Instead of using a branch I recommend that you use a Lookup Issues action . To get the count of issues returned, use the smart value {{lookupIssues.size}}

[Dave Furlani]

Ah, of course. I'm an idiot. I forgot about Lookup. Thank you @Trudy Claspill

[Dave Furlani]

The final version, which seems to do what we need, should anyone else be trying to do something similar in future