Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Sometimes automation rule doesn't run and it doesn't display anything in the audit logs

Abhishree Nagesh
Contributor
March 26, 2019

Hi,

Using Automation for jira for the auto update of the status from jira software project to jira service desk project.

We have written the rule for one particular project .(global rules)

Sometimes the status in audit logs shows success , But when  it shows no action performed,if it is viewed in detail then jql query condition is not meet is display and issue key would be of different project .

Sometimes rule doesn't run and it doesn't display anything in the audit logs.

please provide the solution ,it is blocker in the production server.

 

Regards,

Abhishree Nagesh

1 answer

0 votes
Laurens Coppens
Community Champion
March 27, 2019

Abhishree,

For this case i think its best to open a support case with codebarrel, they have great support for their automation plugin.

If you want to get support here in the community its best to share some more details about the rule:

* What is the trigger

* Why is it a global rule when you only use it for one project?

* What is the jql

 

Regards,

Laurens

Abhishree Nagesh
Contributor
March 27, 2019

Hi, 

@Laurens Coppens 

Thanks for your quick reply.

I have raised the ticked to the add on vendor also, waiting for their reply.

There are three types of rules created,

1.auto creation of issue(from jira service desk to jira software)

2. auto copy of comment (from jira software to jira service desk)

3.auto update of status.(from jira software to jira service desk)

First two are working fine.but not the auto update of statusCapture of rule.PNGcapture 2 of rule.PNGScreeshot of audit log.PNG

Please find the attachment for the trigger and jql query

Laurens Coppens
Community Champion
March 27, 2019

As the log says, the jql condition was not met.

So you need to check the original ticket EASYREWARD-18 to find out why.

Also check the history log of that ticket because it could be that the issue meets the jql at this point, but not when the rule was triggered.

The jql is not fully visible in the screenshot, but i see it doesn't only check the project but there is also an "AND" clause, maybe there is a problem there?

Suggest an answer

Log in or Sign up to answer