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

Why are no actions being performed when my JQL finds issues when testing within the automation?

Renee Troiani

I created a scheduled automation to email the assignee of certain issues. When I validate my query, it tells me it has found an issue. However, when I actually run the rule, it says there were no related issues found.

The automation: Scheduled trigger (running it manually for testing purposes)

JQL: status != DONE and summary ~ donation and assignee = Jennipher

THEN: email assignee

Accepted answers

Bill Sheboy

Hi @Renee Troiani

Following this thread, I did not see this information yet so I wondered...

1) What is the scope of this rule: is it global or for one project?

2) Have you tried adding the project (i.e., BA) to that JQL statement to observe the impact? For example:

project = BA AND status != DONE AND summary ~ donation AND assignee = Jennipher

3) Has the name of that user changed over time, from another value prior to "Jennipher"?

4) How many active users are named "Jennipher"? Just one or more?

5) For some reason, automation rules can get "glitched" and broken if edited to many times. (I do not know why; there is something happening with the editor.) Have you tried to disable this rule, recreate it from scratch, and then test to see the results?

Kind regards,
Bill

All comments

Trudy P Claspill

Hello @Renee Troiani

Can you please show us the details of the automation rule, please? It is challenging for us to diagnose the issue without those details.

Does your trigger include the JQL, or is that a separate component of your rule?

Dan Tombs

Hi @Renee Troiani

I think what you may be struggling with is a checkbox on the schedule trigger that only runs for issues updated since last run. Make sure that isn’t checked.

Trudy P Claspill

That is my suspicion also.

Renee Troiani

Screen Shot 2023-07-26 at 5.19.44 PM.png Hi @Trudy P Claspill So sorry, didn't think to include a screen shot. That box is indeed unchecked! Note: The 5 minute scheduling is just for testing purposes

Renee Troiani

Hi @Dan Tombs , I added a screenshot to the response below, sorry I should've done that initially!

Trudy P Claspill

When you click the Validate query option you said it is indicating that it found an issue. You should be able to click on the issue count and it should take you to the Search screen and show you the issue(s) it found. Can you do that and confirm there are issues listed.

I ask this because using "assignee = Jennipher" should not actually find any matching issues. Using "assignee" in search criteria will actually search for a matching user account ID. When you plug such criteria into the search screen you can type in the name of a user, and the search screen will automatically convert that to the appropriate ID.

Screen Shot 2023-07-26 at 4.27.31 PM.png Screen Shot 2023-07-26 at 4.28.17 PM.png

If you want to use "Assignee=" in a JQL in a rule you need to first use it in the Search screen to get the Account ID conversion, then copy that to the rule.

Renee Troiani

Screen Shot 2023-07-26 at 2.20.45 PM.png Unfortunately, it does find the correct issue (I created a test issue to specifically fit the JQL search)

Bill Sheboy

Hi @Renee Troiani

Following this thread, I did not see this information yet so I wondered...

1) What is the scope of this rule: is it global or for one project?

2) Have you tried adding the project (i.e., BA) to that JQL statement to observe the impact? For example:

project = BA AND status != DONE AND summary ~ donation AND assignee = Jennipher

3) Has the name of that user changed over time, from another value prior to "Jennipher"?

4) How many active users are named "Jennipher"? Just one or more?

Kind regards,
Bill

Renee Troiani

Hi @Bill Sheboy ,

1) The scope of this automation is this specific project

2 and 5) I just tried recreating the automation after turning the first one off and added the project specification. I got the exact same results as the first automation

3) The user name has never changed values

4) There is only one active user named Jennipher

Thanks so much for the reply!

Bill Sheboy

Hmmm...

Is this a team-managed or a company-managed project? You can see that information at the bottom of the left-expand area on the page.

My next idea would be "I wonder if someone has either altered the permissions of the Automation for Jira user, or severely locked down permissions in your BA project." Neither of those seem likely, and your Jira Admin could confirm that.

Renee Troiani

This is a company managed project. I do have administrator permissions on this project, not sure if that makes a difference.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jql

automation

jira-service-management-cloud

jira-service-management