Extremely simple automation is not being triggered for all types of issues

[Kyle]

Just started using the new Jira automation in Jira Software Cloud. I created a very simple automation to email the reporter whenever an issue is created - just for test purposes. When I create a "To Do" issue it fires as expected and sends the email. However if I create any other type of issue (Defect, Requirement, other custom issue types that we have) the automation is not triggered and I get no email. What am I missing?

Here is the automation. There is no clause that checks for the type of issue:

It is scoped to a single project and it is enabled:

When I create a new "To Do" issue in that project, the automation fires and I get an email. When I create any other kind of issue in that project, no run of the automation and no email.

[Kyle · Accepted solution]

Atlassian support pretty quickly found the problem. I had customized some of the workflows and had added my own post function on the Create action.  The automation needs the "Create Issue" event to be sent at the end instead of my custom event which makes total sense. I wasn't even using my custom even - I had just been experimenting.

Here's the bad post-function configuration:

I edited my workflows that had this, went to the create action, edited the post functions, and changed the last one to fire the "Create Issue" event instead.  The good post functions look like this.

[John Funk]

Hi Kyle - Did you check the Audit log to see if it helps you any? From what you described, it should send an email every time an issue is created on that project, regardless of the issue type. 

[Kyle]

Yes I looked at the audit log and it isn't helping. I do see a SUCCESS audit log entry when I submit a To Do issue and I get an email. There is no audit log entry at all when I submit the other types of issues - nothing indicating failure or errors or anything. And when I look at the issue > Automation > Rule Executions information the To Do issue shows the rule execution and the other issues show no rule execution.

[Jack Brickey]

Seems odd on the surface. You mention a “To Do” Issue. Is that an Issuetype? To Do is typically a status so a bit confusing. What other issuetypes do you have? What is uniques about them? Different workflows?

[Kyle]

Yes "To Do" is one of the issue types in that project. Here are the 10 issue types in the project. When I submit a "TODO" or a "Requirement" then the automation fires correctly on the issue creation. When I submit a CMR or LCMR or Defect the automation does not fire on issue creation. Each of the issue types has its own workflow. Even the two that do work - TODO and Requirement - have different initial statuses.

There's no mention in the automation documentation that it is limited to certain issue types, or out-of-the-box issue types vs. custom issue types, or limited to issue types that have a certain first status. That's what I can't figure out.

[John Funk]

No, there is nothing about Issue Types in your rule that should prevent it from sending an email for the others. That would be handled with a Condition. 

Maybe there is something in the workflow for the other types that is preventing it for some reason? I can't imagine what that would be. 

I would go ahead and create a Support Request for Atlassian here:

https://support.atlassian.com/contact/#/

[Kyle]

Thanks for looking. I submitted a support request and I'll reply back here with their resolution: https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-568068

[John Funk]

Awesome - thank you and good luck!