New Automation Rules Not Functioning

[Vivek Dubba]

I have created an automation rule to notify me when any ticket in a given project is in a particular status for 2 weeks.

The automation is currently set to:

When:

Status Changed

If:

Issue matches status = "On Hold"

Issue matches "Project name" = given project

Issue matches timeestimate >= 14d

Then:

Alert user x (where "x" is my email address which is a Jira admin user)

This same rule was previously based on an SLA but that did not work either.

[Dane Kantner]

project= implies you're searching outside of the same project the rule exists in, or you wouldn't need that filter. You can no longer do cross-project lookups if the rule is single scoped to a single project, you need to convert it to multi-project. 

AFAIK this was always the intention but there was a bug and they deployed a fix that changed how these rules work, this change was made in our Jira cloud instance around 1am Central early the morning of 1/21/21. We had tons of rules that were previously doing project= or issueLink= in the lookup to another project and they all broke at that time. Atlassian premium support confirmed it was no longer possible in single scope.

The implications of this are you then need to be a jira global admin to manage the rule at all, and also the count of executions per day allowed is based on your licensed user count x100, there was no limit in single scope project rules.

[Vivek Dubba]

Thank you for the response. I'm afraid that removing the project = did not enable the automation to work. Not sure what else to do at this point. Does Jira version matter when it comes to automation rules by any chance?

[Dane Kantner]

the rule is set up in the same project that you're trying to modify issues in?

[Vivek Dubba]

Hi Dane,

Yes, that's correct.

Thanks,

Vivek

[Brant Schroeder]

@Vivek Dubba I would suggest creating a filter that identifies these issues and then subscribing to that filter.  This will give you a daily report of all issues that have been in the status for more than 14d.   https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-3-of-4

You can use something like this "status changed to "On Hold" before -14d AND status was not "NEXT STATUS IN WORKFLOW" after -14d AND status = "On Hold"

[Vivek Dubba]

Hi Brant,

Thanks for the response. We don't want to use filters for everything, we have need for an automated notification of ticket statuses. We run a 24/7 shop, and all that entails.