Automation Error

[Ömer Gündüz]

Hi Experts,

I am trying to configure an automation in a Data Center environment. However, even though it is within the project scope and I have kept the conditions quite simple, the automation is not being triggered. Additionally, there are no entries appearing in the audit log.

I have tried using different triggers such as create, transition, update, and value changed, but none of them are firing.

What could be the reason for this issue? Do you have any suggestions?

Regards

[Arkadiusz Wroblewski]

Hello @Ömer Gündüz 

if there is no audit log entry at all, then I would look first at the trigger side, not at the conditions.

In Automation for Jira DC, no audit entry usually means the rule never picked up the event in the first place. So I would first verify that the rule is enabled and then check whether the Jira event you expect is actually being fired for create / update / transition in that workflow.

The actor permissions are still worth checking too, but from your description the bigger clue is the completely empty audit log. That points more to trigger/event handling than to a later rule step failing.

[Ömer Gündüz]

Hello @Arkadiusz Wroblewski 

The rule is active, and when I validate the JQL condition using the “Validate Query” option, it returns issues. However, despite this, the rule does not run and does not trigger under any circumstances.

Even when I remove all conditions and leave only a simple log action, it still does not trigger. At this point, I’m unable to determine how to resolve the issue.

[Marc -Devoteam-]

Hi @Ömer Gündüz 

It seems the actor of the rule has no access on the project.

[Ömer Gündüz]

Even though I set the rule's actor to the system administrator, the rule still isn't working. @Marc -Devoteam- 

[Marc -Devoteam-]

Hi @Ömer Gündüz 

Based on your reply, who removed this action, as this is normally a default action on the create transition.

[Ömer Gündüz]

I don’t have any information on that, but I’ll look into it. @Marc -Devoteam- 

[Enric Font]

Dear @Ömer Gündüz 

Has the actor of the rule permissions on that project?

This is the only automation rule not working?

[Ömer Gündüz]

@Enric Font, it appears that the owner of the automation rule has permission to  access the project.Even if I assign a system administrator, it still doesn't trigger

[Enric Font]

Dear @Ömer Gündüz 

A system administrator may not have access to a specific project as a user

[Ömer Gündüz]

Yes, you are right, but I also checked with the permission helper whether the user has access and can edit the issue. @Enric Font 

[Enric Font]

Could you please:

1. change the trigger to a Manual execution
2. go to a matching issue and execute the rule manually
3. Check if the rule is executed?

[Ömer Gündüz]

When I did it manually, it recognized the trigger and returned a success. But I don’t understand why it can’t enter it automatically. @Enric Font 

[Ömer Gündüz]

I created a new record, for example, but it still didn't capture the change when the field value changed. The log was still empty. @Enric Font 

[Enric Font]

In your workflow, in the create transition postfunctions what event are fired?

[Ömer Gündüz]

I think I’ve found the issue. The automation wasn’t running at the create stage because the workflow didn’t have a created listener. When I updated the listener to a created listener for testing, the rule worked. So, where are these events defined, and how can I view their purpose in the system?

[Enric Font]

Dear @Ömer Gündüz 

But you have to keep in mind that it's not very common to update the created event during the creation transition. If it was changed, it must have been for a reason. If you change it, other functionality might fail.

[Ömer Gündüz]

Thank you very much for the information; I will pass this on to the relevant people and we will discuss the matter @Enric Font