Automation

[madhu.tejas]

I have created an Automation trigger to send mail action for all the new issues types created based on the Custom field value condition. but apparently it does not work most of the time.

Can you please suggest 

[Pramodh M]

Hi @madhu.tejas 

Since you are checking for Issue Create Trigger Event

The Best Practice would be to add the Re-fetch Issue Data Action before checking any condition

Let me know if it works

Thanks

[madhu.tejas]

Hello @Pramodh M , Thanks for the response.

I tried that too ,but the same results.

when worked some time

[Pramodh M]

Your question's screenshot and Reply screenshot are not corresponding to the same rule.

Did you change the rule?

[madhu.tejas]

Yes i tried to change the rule again after (as seen original screenshot)- removed Refetch option. 

trying different ways to make it work

[Bill Sheboy]

Hi @Pramodh M 

Just an FYI...

I also recommend adding the Re-fetch Action after the Issue Created trigger when such symptoms occur...and I would not characterize it as a "best practice".  It is a work-around for a defect in the automation engine and/or REST API, whereby the event is firing before the event has completed processing.  Hopefully this will be fixed one day and this extra action will not be needed.

Kind regards,
Bill

[Rilwan Ahmed]

@madhu.tejas 

When you say "most of the time", does it work in some cases. If so, check the automation audit log for failure step. 

[madhu.tejas]

Hi, Yes but the audit log doesnot give teh right recommendation. I have tried all

Adding the screenshot when it worked and when it doesn't

- When Email was sent successfully 

- Same condition when it was not sent successfully

 

. Nothing changed in between.

[Rilwan Ahmed]

1. How is assigment group updated ? Is it a required field while creating ticket or its  updated later by any other automation rule ?
2. Run the jql used in automation and check if it gives any result.
   
   

[madhu.tejas]

Thanks @Rilwan Ahmed 

When a ticket is been created , assignment group is manually selected from the dropdown list

I also tried the with JQL same result, it worked before and now not.

[Rilwan Ahmed]

@madhu.tejas 

If the JQL is not fetching any result, then

• It could be there are no tickets matching the condition
• As its a custom created field, the indexing is not working properly.  -- Request you to run project re-index OR the whole system re-index once. 
• May be some changes done in field configuration. 

[madhu.tejas]

@Rilwan Ahmed  In Jira re-indexing is automatic in Cloud edition now.

Also even i try with JQL condition criteria check is fine, but when published is doesn't satisfy the criteria when rule executes :(

I tried with With and with JQL criteria and also just with JQL criteria.

Looks like there is something else to is that i am missing.