nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Issue Created" event not triggered via Issue Collector

Marco Maetzler

I have automation rules that use the "Issue Created" trigger to check a few things. I realized that automation rule gets trigger without a problem when the issue is created within Jira. But issues created via an Issue Collector that is embedded on an external website do not trigger the "Issue Created" event.

I was able to reproduce it with the simplest of rules:

If the issue is created via an Issue Collector, this rules does not get triggered and does not show up in the audit log. Is this missing trigger a defect or is this the intended behavior?

Thanks!

Accepted answers

Marco Maetzler

Quick update: This only happens if the "Report" for the issue Collector is set to "Automation for Jira".

For cases where the reporter is "Automation for Jira", the new issue trigger does not seem to work.

For such cases, a workaround is checking the "Allow rule trigger" checkbox, which will solve the problem (or choosing another value for "Reporter").

I still believe that this is a bug in Jira, but I now have a workaround.

All comments

Ravi Sagar _Sparxsys_

Hi @Marco Maetzler

This is interesting, I don't know if this is a bug in automation. May be you can try to create a post function to trigger a webhook or update a field after issue creation.

Ravi

Marco Maetzler

Hi @Ravi Sagar _Sparxsys_

Thanks for the reply. Yes I was in fact able to cobble something together with post functions. But I wanted to check here with community to see if this should get reported as a bug or if Collectors are intended to be allowed to skip those event triggers.

Ravi Sagar _Sparxsys_

Great. Yes, it should be a bug in my opinion and it will let other know about this behaviour.

Marco Maetzler

Quick update: This only happens if the "Report" for the issue Collector is set to "Automation for Jira".

For cases where the reporter is "Automation for Jira", the new issue trigger does not seem to work.

For such cases, a workaround is checking the "Allow rule trigger" checkbox, which will solve the problem (or choosing another value for "Reporter").

I still believe that this is a bug in Jira, but I now have a workaround.

Bill Sheboy

Hi @Marco Maetzler

That is an interesting approach as the "Allow rule trigger" option is documented to allow one rule to trigger another through its actions. This seems to imply the issue collector is being identified as an automation rule (i.e. triggering event) via the initiating user...

And...that the runaway looping logic of the automation engine can be circumvented by changing the initiating user. Very curious, and perhaps risky to cause rules to run too fast and so trigger one of the other SLA safeguards to halt processing: processing time/24 hours, etc.

Thanks for this information!

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation