Suppress "Conditionally skipping execution" warning in JMWE

[Brandon Ibach]

We're using Jira Data Center v9.4.6 and Jira Misc Workflow Extensions v8.2.0.  Our workflow includes a number of JMWE post-functions with "Only if condition is true" checked.  These all work as intended.

However, in trying to keep an eye on JMWE's "Execution logs" screen to find and fix any cases where things are not working as intended, we're seeing many "Conditionally skipping execution" warnings, which make it difficult to monitor these logs for actual problems.

Is there a way to suppress these superfluous warnings?

[Ajay Singh _Appfire_ · Accepted solution]

Hi, @Brandon Ibach ~ I am from the Jira Misc Workflow Extensions dev team. On the Execution Logs page, you should be able to suppress these warnings by unchecking the checkbox and then downloading the JSON file to analyze error details.

I am sharing the screenshot from the latest version of JMWE. Please note that on the version of JMWE, you are using, the Warnings checkbox is placed on top right above the chart.

Here is the link to the doc.

If you still have any further questions, feel free to reach out to our Support team through Appfire's Support portal.

Cheers!

[Brandon Ibach]

Hi, @Ajay Singh _Appfire_.  Thank you for the prompt response.  I appreciate you pointing out the filtering options.

However, unchecking the Warnings box hides _ALL_ warnings, some of which may be important to consider, as they may indicate a possible problem.  In the cases I describe, JMWE is doing exactly what I told it to do, skipping the action because the condition was not met.

I'd like to keep my logs free of warnings by fixing things that cause them, but there's nothing for me to fix, here, because it isn't broken.  Arguably, these log entries should even be shown as Successes, rather than Warnings.

Is there a way to filter out just these types of warnings, or configure JMWE not to log them?

Thanks!

[Ajay Singh _Appfire_]

Hi @Brandon Ibach - let me bring this to my dev team‘s attention. I will provide you an update by tomorrow (around same time or before). 

Cheers!

[Ajay Singh _Appfire_]

@Brandon Ibach ~ I discussed your post with JMWE developer. Unfortunately, there is no workaround for it but the good news is, it will be addressed as part of our next release. There is an improvement ticket (https://appfire.atlassian.net/browse/JMWE-1927) for it. Feel free to add yourself as a watcher.

Cheers!

[Brandon Ibach]

@Ajay Singh _Appfire_ Excellent!  Glad to see this was already on the team's radar.  I'll keep an eye out for this enhancement.  Thanks!