Unable to run a project automation

[Melody Wong]

I setup a simple automation to run when a ticket is created by a specific user. I noticed in the audit log that the config change was logged but this rule has never run. I am the "Actor" of this rule and all the proper permissions (ability to view and comment) were assigned to me. How can I get this automation to run? All posted documentation in the community points to a manual way to run this, but I am not seeing an option.

[Fabian Lim]

Hi @Melody Wong

Welcome to the community!

Issue updated doesn't work for changes in assignee: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

You will need to use the issue assigned trigger and then use a condition to check the actual user.

Regards

[Melody Wong]

Hi @Fabian Lim

I've created a rule to mirror what you've suggested. I am still not seeing the rule run. Is there something else I'm missing?

Thanks,

Melody

[Fabian Lim]

Jack is correct.  You should use the issue created.  I thought you were checking after being updated.

Regards

[Jack Brickey]

Could you please share audit log details?

[Jack Brickey]

You mention "to run when a ticket is created by a specific user" but that isn't what either image projects...

trigger - issue created

condition - reporter = xxx

action - ???

[Melody Wong]

@Fabian Lim @Joseph Chung Yin 

Sorry attached the wrong screenshot. This is my automation with the issue created trigger and the condition being if I am assigned. 

I have created a new ticket and i'm still not seeing this automation working.

Attached above is a copy of the audit log.

[Joseph Chung Yin]

@Melody Wong 

Thanks for the updated screenshot.

Was the assignee for the issue got populated at issue creation time?  Or it is done after the issue was created?

If your test case where assignee is added after the issue is created, then your rule will never fired.

Can you check on that?

Best, Joseph

[Melody Wong]

Hi @Joseph Chung Yin , 

The assignee was assigned at the point of issue creation. The updated and created time stamp for the issue is the same. Therefore there were no updates after creation.

[Joseph Chung Yin]

@Melody Wong -

Can you try to create another issue for your project and send us another screenshot of of the audit log?

It is because your latest screenshot didn't have anything else beside the configuration was changed from your rule.

Another thing for you to check would be that if the rule was created in the right project or not.  If the rule was created for Project A, but you were conduct testing against another project, thus the rule will never be triggered from your issue creation operation in the other project.

Best, Joseph

[Melody Wong]

@Joseph Chung Yin 

Here's a screenshot of a new ticket created

Here's a screenshot of the automation audit log. No updates have been logged since the configuration, even though there's a ticket that should have triggered this automation.

Here's a picture of the configuration, the scope is set to project "SR" and as you can see from the first screenshot the project matches the scope.

[Joseph Chung Yin]

Very strange that there are no logging of anything in the audit log.  At this time, I would recommend you contact your system admin to look into the system logs for any error or contact Atlassian Support team for further assistance.

Best, Joseph

[Melody Wong]

Are there any permissions that should be given or anything I need to install for the automation to work? What's the way to reach out to the Atlassian Support team?

[Joseph Chung Yin]

For Atlassian Support - https://support.atlassian.com.

Because you already have the ability to create rules via Automation for Jira, it means it is installed and enabled for your env.

However you can check with your system admins to ensure that this add-on is setup properly by Clog wheel (Jira Administration >> Manage Apps and look for Automation for Jira.  It should look something like below ...  (make sure all modules are enabled)

Best, Joseph

[Joseph Chung Yin]

@Melody Wong -

Welcome to the community.  As mentioned by @Jack Brickey , please provide what is the audit log.  In the audit log, it will give you more information (details) on why the rule is not fully executed.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.