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

Help with JQL Automation Statement

Heather Marquez

Hello,

I'm new to writing JQL and all the many tutorials and posts have not helped me solve this after dozens of iterations.

I'm implementing an automation rule that if issues are in certain status/field situations that an email would be auto generated to the reporter.

The trigger is a daily run at a certain time (e.g. end of day), then the trigger will look for issues in certain status. Currently I have this written as

{{lookup.Issues}} 'IN' status = Processing 'OR' status = Received

I'm very sure what I'm writing here is wrong and error messages confirm but I cannot seem to get the right syntax. Thank you in advance for your time and help!

Screenshot 2023-09-25 at 12.47.26 PM.png Screenshot 2023-09-25 at 1.39.33 PM.png

Accepted answers

Trudy P Claspill

Hello @Heather Marquez

You cannot use a smart value in the JQL that is within the Schedule trigger.

Remove the {{lookup.issues}} IN portion of that JQL.

You can also add the two conditions that follow the trigger into the JQL in the trigger:

status in ("Processing","received") and issueType="Port a Number" and Labels in ("pending_customer")

And, here is some free training from Atlassian to learn more about using JQL (thanks to @Bill Sheboy who posted these on another Question):

All comments

Trudy P Claspill

Hello @Heather Marquez

You cannot use a smart value in the JQL that is within the Schedule trigger.

Remove the {{lookup.issues}} IN portion of that JQL.

You can also add the two conditions that follow the trigger into the JQL in the trigger:

status in ("Processing","received") and issueType="Port a Number" and Labels in ("pending_customer")

And, here is some free training from Atlassian to learn more about using JQL (thanks to @Bill Sheboy who posted these on another Question):

Bill Sheboy

Hi @Heather Marquez

Adding to Trudy's answer...

Would you please describe the problem you are trying to solve by doing this?

You seem to be sending notification emails to the reporters of the issues for some type of notification. Do you want to send one email for each issue or to send one email to each reporter (with a list of their issues)?

Kind regards,
Bill

Heather Marquez

Thanks Trudy! The changes seemed to have worked well. Have been taking the tutorials too so appreciate sharing those!

I am running into a "Throttle" issue

@Bill Sheboy

The goal is to take all issues that agents were tagged in a given 24hr period and send one email daily to the reporter notifying them of the information required to resolve their issue. Generally a reporter will only have one issue ticket so it is one email for each issue.

It seems that Trudy's suggestions work great but now running into a Throttle issue. Based on the screenshot I just added here, is Jira looking at all issue tickets and not just the ones I filtered on (e.g. Issue Type, Label)? I only have 13 tickets in those states and that falls under the default requirements for allowed service limits.

Thank you so much in advance for any additional light you can shed on this!

Screenshot 2023-10-01 at 8.38.49 AM.png

Trudy P Claspill

@Heather Marquez

The throttling is being applied based on the JQL in the trigger. If you add the Conditions as part of the JQL in the trigger, rather than applying them after the trigger, that should alleviate the throttling.

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