Take a look at the new features:
We have made ten of JMWE's post-functions more flexible by allowing you to specify the target issue(s). Options for the target issues include:
Five post-functions are now deprecated in favor of better alternatives
Since the above post-functions are now more versatile, we have deprecated several post-functions that operate on Linked issues, such as the Clear fields of linked issues post-function. They are now marked as deprecated, and it is recommended to use their generic version (e.g., the Clear fields post-function) when adding a new post-function.
The new Build-your-own (scripted) post-function allows you to run an arbitrary Nunjucks script. This can be used to make REST calls to external systems or to make calls to the Jira Cloud REST API.
The Build-your-own (scripted) post-function makes use of our proprietary, interactive editor and tester, which greatly simplifies scripting. It displays what the script should return, provides a description of global variables that are available to use in your scripts, gives an explanation of how to access any issue field, lists methods and properties available on issue objects, and more.
You can click your way through scripting using the shortcuts provided, or use them for guidance and just write your own. With our intuitive editor & tester, and advanced documentation, you can quickly learn how to create sophisticated workflows, even with minimal coding experience.
You can also test your scripts against any issue to deploy your workflows bug-free.
As of April this year, you can schedule JMWE post-functions to run against issues returned by a JQL search with Scheduled Actions. You can set up many automation types, such as workflow transitions, issue status updates, and user changes, all based on your predefined schedules. However, you can now run any of your Scheduled Actions on demand with the new "run now" button to immediately run a scheduled action.
Tip: You can apply a one-time action to a set of issues, however, it can only run on up to 1000 issues at a time, and you'd need to set up a temporary schedule (i.e., to run once per year) to trigger the "run now" option.