Scheduled Automation - No Actions Performed even though it is finding issues that hit the JQL query

[Richard Blakemore]

Good Day,

I was wondering if someone can help with this automation I have created.

The Automation is fairly simple.

• Using a CRON schedule - every 8 hours it checks a JQL query
• The JQL query, searches a Project for Issues that don't have an Assignee
  • As of today this has found 3
• It then does a If Statement looking at the passed Issues from the JQL 
  • If Assignee = Empty
  • Run a web request.

The issue I am having is that

The JQL query in the schduled trigger is finding issues, but not triggering with the "No Actions Performed" response in the audit.

I was wondering if someone could advise or let me know what I am missing?

This did work before the 10th June but since then it hasn't.

the JQL used is as follows:

project = ****** AND issuetype in (Bug, Story, Task, Test, Sub-task) AND status = Open AND reporter = ****api account*** and assignee is empty

[Kseniia Trushnikova · Accepted solution]

Hi @Richard Blakemore,

Can you please share more details from the rule log? Do you have the entry "No related issues could be found"?

[Richard Blakemore]

Hi @Kseniia Trushnikova 

That is correct - 

Action details:

Scheduled

No related issues could be found.

Associated items:

None

the JQL query in the schedule is seeing 3 issues so I thought it would send these 3 to the next step, as the below is selected.

When rule executes...

run a JQL search and pass results to subsequent conditions and actions

[Kseniia Trushnikova]

@Richard Blakemore, it seems that every time the rule is executed with cron, JQL returns no issues. For example, such tasks may be at 5 am, but may not fall into the filter at 8 am, when the rule is triggered if someone has changed them (for example, set Assignee or changed the status).

Can you manually trigger the rule by clicking the button Run rule when you're sure there're issues in your JQL?

[Richard Blakemore]

Hi - I just saw the rule run again at 09:00BST and it failed

I did check the JQL before and made sure there were issues being found from the JQL - 3 issues to be exact

It just doesn't seem to be sending the found issues from the JQL to the rest of the automation

[Kseniia Trushnikova]

@Richard Blakemore, that's interesting. What if we copy this rule and build it a little differently?

Try to use Fixed rate of every 8 hours, add your JQL and check Process all issues produced in bulk:

Then delete the condition as "Assignee is empty" is already present in JQL and add the "Log action" with "{{issues.size}} issues found." to write the entry in the rule log:

Run this rule copy and let me know the results from the log.

[Richard Blakemore]

Thank you for your comment  - I tried this and it still didn't work

I did get it work by creating a copy of the flow and it worked on the new flow .. no clue why the old one didn't and the new one has!

Thank you for your help