Unable to trigger Automation from Asset custom field

[Troy Edmonds]

I have a custom Portal form that uses local government council. zones 

the field is linked to Jira Assets DB 

its driven by only one project rule

I've tried a few different setups, and nothing is triggering to auto assignment 

tried just 1 LGA and it doesn't work either

no errors in the Log ?

maybe I'm just tired but everything I tried failed

[Bill Sheboy]

Hi @Troy Edmonds 

First thing, for a question like this please also include an image of the audit log details showing the rule execution.  That will provide context for which steps happened, and other indications.

Until we see that...

Next, your rule conditions seem to be testing for LGA values and then making an assignment for different values.  When you want to do that, please use the if / else condition structure.  Otherwise the rule will halt after the first condition does not match.

For example, please try...

• if / else condition
  • issue field condition: LGA equals Albury City Council
  • action: assign user X
• else / if
  • issue field condition: LGA equals Byron Shire Council, or ...
  • action: assign user Y
• ...

Another way to do this is with a Lookup Table, where the LGA value is the "key" and the "value" is the account id for the user to assign: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798

Finally, when using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after that trigger.

The reason is that trigger can fire so quickly some issue data may not yet be available to the rule.  The result is some conditions and rule actions may behavior in unexpected ways, or possibly even cause errors.  Adding the Re-fetch Issue will slow down the rule a bit by reloading the data before proceeding.

Perhaps add that action and re-test your rule.

Kind regards,
Bill