Conditional Execution on Send Email Post Function not working with previous JQL
In our previous version of JIRA Software 7.1.1 with the 2.2.30 version of the plugin the conditional execution worked with JQL like %{00000} in ("Text") After upgrading to JIRA Data Center 7.3.3 this conditional no longer works. It is still validated by the Syntax checker as correct, but the email is never sent. I was able to get my workflows working again by changing the JQL to %{00000} ~ "Text" We use these all over our workflows and it will be extremely tedious to change them all to the working syntax.
Is this a regression?
Comments (8)
-
repo owner -
reporter The first image should give you the title of the workflow post function. I have circled the conditional execution section that I had to change in the second image.
Matthew Harkins | Systems Engineer Bats Global Markets, a CBOE company Office: 913-815-7123 | Mobile: 913-515-2656 www.bats.comhttps://urldefense.proofpoint.com/v2/url?u=http-3A__www.bats.com&d=DwMFAg&c=MSu_UsKK7we0hjvEwhbzFA&r=zb6LQMrFcA_Jgx7OZjeY6g&m=u2mkk5pkt55jME8SvnX6s-5lhKp5fJr9cc9uOiJQles&s=3yCfOrW7wTe_m4MXsOkwwLySghZCWFQgYFOdqnbDbUE&e=
Learn more about the CBOE and Bats integration at CBOE.com/BatsIntegration<cboe.com/batsintegration>
-
repo owner Sorry, Mathew, but you haven't actually attached any screenshot to the issue. I can only see fragments of an URL in your post.
-
reporter - attached sendemailFunction2.JPG
- attached sendemailFunction.JPG
Weird, I see the two attachments on my sent message.
I'm now trying to add the attachments through the GUI instead of via email attachments.
-
repo owner Matthew,
That's not a JQL query, but a boolean expression in JIRA Workflow Toolbox's particular language.
The following 2 expressions are not equivalent:
%{00000} in "Text"
returnstrue
only when the whole issue summary is contained as a substring in"Text"
string.%{00000} ~ "Text"
returnstrue
only when Summary contains"Text"
substring.
I imagine that your desired behavior is the second one.
The behavior of those string operators have not changed since they were included in the plugin.
-
reporter I have a custom multi-select field with text options "US" and "UK" It is possible that I only tested 1 option at a time instead of both, but I was "nearly" certain that before the upgrade, I could have an issue that had both options selected and when the transition occurred independent post process functions would send emails according to the summarized post processes conditions: post process function 1 had a boolean expression for example %{12345} in ("US") post process function 2 had a boolean expression for example %{12345} in ("UK") In any case, I have adjusted the expressions to the case %{12345} ~ "Value" per your response and my processes are now working -- perhaps more accurately than before. Thank you for the precise explanation.
-
repo owner Glad you made it work.
You can also use a boolean expression like
"US" in %{nnnnn}
, which is equivalent to%{nnnnn} ~ "US"
, where nnnnn is the field code for your Multi-Select custom field. -
repo owner - changed status to resolved
- Log in to comment
Hi Matthew,
Which feature of the plugin are you using?
Can you please attach a screenshot of a feature using that JQL query?