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; } } }

Has there been any changes in what counts as a automation rule trigger/activation?

Stefan Salzl_kpt337

As I came back from vacation i was kinda shocked about a mail from atlassian telling me I´m running out of my automation limit. I then checked activations of my rules and indeed they kinda exploded.

When I created an tested my rules (I swear I remember it was like this) then the rules JUST wrote an activation/run when both the trigger WITH its condition matched. Otherweise jira didn´t even notice a run/activation and didn´t count a record for that.

My example:
Atuomation rule should run and do something (doesn´t matter what) when a UserStory is created.
So the trigger is "create issue" with condition "issue type equals UserStory".

Now this rule gets activated and counted as a run of an automation rule EVERY TIME an issue (no matter which issue type) is created.

imho the condition "issue type" only makes half sense....

...and I swear there was no activation when I left into my vacation 2 weeks ago

Could someone please help?

Accepted answers

Bill Sheboy

HI @Stefan Salzl -- Welcome to the Atlassian Community!

Would you please post an image of your rule?

It seems from what you are describing that the rule is firing because the trigger occurs and then the condition stops processing. Providing the image will help the community give you more information and advice.

Thanks, and best regards,

Bill

All comments

John Funk

@John McKiernan - Can you verify one way or the other?

Bill Sheboy

HI @Stefan Salzl -- Welcome to the Atlassian Community!

Would you please post an image of your rule?

Thanks, and best regards,

Bill

Stefan Salzl_kpt337

How could it be the other way round?? As I understood the condition refers to the trigger so the rule only fires when the event matches the trigger and its condition.

John Funk

The rule fires based on the trigger - regardless of the Condition. Whether it does anything or not after it fires depends on the Condition. But it has still fired.

Bill Sheboy

Yes, and... I believe there is an execution limit for global rules, not the project-level ones. If you can put your rule at the project-level, executions appears to be unlimited, and there are other constraints:

https://confluence.atlassian.com/jirasoftwarecloud/faqs-for-previous-automation-for-jira-app-customers-993925346.html

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

John McKiernan

hey @Stefan Salzl ,

It looks like your question has been answered below. Indeed, an execution counts whenever an issue is triggers regardless of the condition beneath. So the suggestion below to convert to a single project rule execution which is unlimited is the best advice.

For other rules, you could use the 'field value changed' trigger which is a more economical trigger but it wouldn't solve any big issues here.

Hope that helps.

John

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