Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JMWE - Action works as scheduled, but not event-based

Jennifer Marple
Contributor
December 26, 2025

I have a common type of issue that arrives, that I'd like to handle via an event-based action. The hang-up seems to be that I need to include a variable/starts with type search criteria. 

When I am editing the event-based action, the JQL accurately finds the issues that I'd expect it to, but when it's enabled and running, it doesn't, the logs say that the criteria weren't matched.

I have a similar Scheduled action for when I see we have several of these building up that I manually trigger, to swoop them up, assign and close. That works fine.

Below are the criteria I have in the JQL for each. I suspect it's the last one that is working on scheduled but not on event-based.


Event based (not working): (has the scope of the CMSS project in a separate line than the JQL)
reporter = "sender@company.com"
AND Summary ~ "COMPANY-PROD"
AND description ~ "Error Description: PO"
AND description ~ "Partner Name: Partner"
AND description ~ "SIC_COMPANY_PROD_Process_Translation_Outbound"
AND description ~ "Transaction Set: 810"
AND description ~ " - C*"

Scheduled (working):
project in (CMSS)
AND status IN ("Waiting for support")
AND assignee = EMPTY
AND description ~ "SIC_COMPANY_PROD_Process_Translation_Outbound"
AND description ~ "Transaction Set: 810"
AND description ~ "Partner Name: Partner"
AND description ~ "Error Description: PO"
AND description ~ " - C*"


The issues that match this pattern (and confirm in the Event-based JQL test when editing) DO match the reporter email address. The part of the error with "PO # - C1989" - the numbers after the C vary. I've tried having "Error Description: PO - C*" as one part of the JQL instead of split, but that didn't work at all, even as a scheduled action. When I split them as I have above, the scheduled one does work, but I haven't been able to get the event-based one to work. I have a different ruleset that looks for a very similar error where the variable part is a value that starts with 6.  Like: 

Error Description: PO# - 654378 found in the 856 document is not found in the PO database. Please check and reprocess the file with correct PO#.

 

 


Summary are like this:

[COMPANY-PROD] - Process Failure - WF Name -SIC_COMPANY_PROD_SFTP_PICKUP_SAP with WF ID: ########

 

Description are like this:

Process failed with following details:

Partner Name: Partner

Transaction Set: 810

Workflow Name: #########

Workflow ID: SIC_COMPANY_PROD_Process_Translation_Outbound

Filename: filename.xml

Status: Failed

Error Description: PO# - C1989 found in the 810 document is not found in the PO database. Please check and reprocess the file with correct PO#.

Dataflow ID: ########

Note: This is an automated system generated email. Please do not reply.




Any suggestions?

3 answers

1 accepted

Suggest an answer

Log in or Sign up to answer
3 votes
Answer accepted
Thiago Wenceslau de Santana
December 26, 2025

Hi @Jennifer Marple

I'm a support engineer at Appfire.

Event JQL filter have a limitation with Wildcards(*) on JMWE. Have you tried replacing the last search criteria with a Nunjucks validator?

{{ issue.fields.description.indexOf("PO# - C") > -1 }}

This conditional Nunjucks will return true when it finds "PO# - C" and, if all conditions were met, the event will trigger.

image.png

Please let me know if that works for you.

Best regards, Appfire support team.

Jennifer Marple
Contributor
December 29, 2025

Thank you, I'm going to implement your suggestion now - and I will likely know if it's working or not by tomorrow. We tend to get a chunk of these each morning, but I've already done them by a manual run of the "scheduled" action for today.

Jennifer Marple
Contributor
December 29, 2025

So I'm adding Only apply to issues that match a Nunjucks condition, with this condition:

{{ issue.fields.description.indexOf("PO# - C") > -1 }}


And from my JQL, I'm REMOVING these (I had them split ridiculously, just trying to get things to work, at one point it seemed the # was causing an issue):

AND description ~ "Error Description: PO"
AND description ~ " - C*"


This leaves my JQL as:
reporter = "sender@company.com"
AND Summary ~ "COMPANY-PROD"
AND description ~ "Partner Name: Partner"
AND description ~ "SIC_COMPANY_PROD_Process_Translation_Outbound"
AND description ~ "Transaction Set: 810"


Saving that change now, and we'll see in the next day if this solves it.

Jennifer Marple
Contributor
December 29, 2025

When testing the Nunjucks expression against the example issue I showed in my original screenshots, I do get a true result. 

Your template ran successfully
Result value
true
Jennifer Marple
Contributor
December 30, 2025

@Thiago Wenceslau de Santana - this solved it, I can see my event-based action working earlier this morning before I signed on. Thank you!

0 votes
Trudy Claspill
Community Champion
December 26, 2025

Hello @Jennifer Marple 

What is the Event you are using in your Event based action?

Can you show us screen images of the details of the Event Based action? I'm not clear where exactly in that action you are using the JQL.

Jennifer Marple
Contributor
December 29, 2025

Hi @Trudy Claspill - the event is "Issue Created" and the JQL is part of the IF SCOPE section. 

I'm going to add in the Nunjucks suggestion that Thiago suggested above and see if that does it. I imagine that it will - I've had to do some Nunjucks bits before for my most complex actions, but it's not something I'm super familiar with, so similar help before has solved the problem.

Here's the original event based action, before I make the above suggested edits.

Pasted_Image_12_29_25__10_40 AM.jpg

0 votes
Jennifer Marple
Contributor
December 26, 2025

Screenshots showing the error occurring:

LogResult.jpg




JQL-from-eventbased.jpg


DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events