Rule not running automatically

[Shilpa G]

[Shilpa G · Accepted solution]

It works fine when it is triggered manually, but doesn't update when it is automated.

[Shilpa G]

@Melo @Jack Brickey 

This issue is now fixed.

The problem was with the Post function. It was calling another event and I changed it to Issue creation and Generic event respectively for both the transitions. 

I reached out to Atlassian support and they helped me fix it.

Thank you for your help.

[CSTI - Soporte]

Hi,

Could you explain how fixed it please? I have the same problem.

[Shilpa G]

@CSTI - Soporte please make the change in the transition where this rule is being called. You have different default functions there. You can edit it to call Issue creation.

[Jack Brickey]

what do you see in audit logs?

[Jack Brickey]

the image you provided is not helpful. I assume you are testing by creating a new issue in the project where this rule exists? when you do that please view the associated log and share the details.

[Jack Brickey]

I dont understand "It works fine when it is triggered manually, but doesn't update when it is automated."

this rule should trigger whenever an issue is created. it isn't a manual rule.

[Shilpa G]

[Shilpa G]

The above can easily be called and fields get updated, but the same does not work on issues created, issue transitioned, etc.

[Jack Brickey]

what happens if you create an issue?

[Shilpa G]

Nothing happens on the automatic rule, the fields stay blank. 

If manually run, the fields get updated.

[Jack Brickey]

i need to see the audit log associated with an issue being created. if the rule does not trigger at all when an issue is created then either...

• the rule is not in the same project where the issue was created
• there is a bug with automation
• unknown reason

[Shilpa G]

@Jack Brickey Please can you share steps on how I can get the audit logs?

[Jack Brickey]

On Aug 10 you replied to Melo with an image of the audit log but it was only for the config change. The point is that The audit log is in that very place where you took that image.

project settings > automation > audit log

find the entry that is associated with the create issue event. It may show success or failure. Click on show more and share the results.

[Shilpa G]

It doesn't show anything only says Config Changes every time I edit it.

CP_POC is a multiple group picker field that I am trying to update.

[Jack Brickey]

Ok. For the project associated with these issues please go to the following location and give me the screenshot. Project settings > Automation 

I want to see the list of rules for that project and please indicate which rule is in question here. Similar to below.

[Melo]

Hi Shilpa,

Could you please provide the audit log for this rule?

Thanks,

Melo

[Shilpa G]

[Melo]

Hi @Shilpa G,

As mentioned, you should check the scope of your rule.

You can do that by going to "Rule details", then select the "Scope".

I would suggest using a single project, like the example below.

[Melo]

Also, if you're not planning to trigger this rule in multiple events, you can choose the trigger "Issue Created" instead of "Multiple events">"Issue Created"

[Shilpa G]

@Melo it is a single project.

It does not work even if I set it to issue created.

[Melo]

Hi Shilpa, that's strange. 

Here are some tips for debugging your rule

https://support.atlassian.com/jira-software-cloud/docs/debug-a-rule/

Also, some information about service limits, but I guess that shouldn't be the case

https://support.atlassian.com/jira-software-cloud/docs/what-are-service-limits/

You can check how many executions you had - I think some cloud subscriptions may have limitations

https://support.atlassian.com/jira-software-cloud/docs/view-performance-insights/ 

I'm not sure if I will be able to help further, if the scope is fine, and if you're creating issues and the rule is not being triggered being triggered. I would suggest opening a ticket with Atlassian support.

Thanks,

Melo