This version brings major new features as well as many improvements:

Highlights of this release:

Shared Actions: reusing post-function configurations

Post-functions (or sequences of post-functions) can now be configured once and then added to multiple transitions across different workflows. You can quickly reuse common configurations, and they are much easier to maintain. Here is how it works: in the Shared Actions, combine one or more JMWE post-functions into an action. Then, use the Shared Action post-function to add it to various transitions, even in different workflows. Read this blog post to learn more.

Scheduled Actions: automating post-functions outside of workflows

Regular workflow post-functions run on transitions, but now you can schedule JMWE post-functions to run against issues returned by a JQL search. Scheduled Actions offer flexibility: you can set up many types of automation, such as workflow transitions, issue status updates, user changes, all based on your predefined schedules. Read this blog post to learn more.

Sequence of Post-functions: ensuring a predictable post-function execution order

In Jira Cloud, during a transition, all post-functions run in parallel. This new post-function, Sequence of Post-functions, allows you to combine other JMWE post-functions into one sequence so that they can all run in a predefined order. The Sequence of Post-functions guarantees the order of events, and replaces the need for using delayed execution. Read this blog post to learn more.

Display Message to User: showing custom messages on transition

Use the new Display Message to User post-function to show a custom message on the issue view page to the user triggering the transition. For example, during the transition that creates a new issue, provide the user with a link to the newly created issue. 

Easily access JMWE’s top features with one click

Jira Administrators can now navigate to the new Overview (a.k.a. Admin Console) page. If you already have the new navigation system, go to Jira Misc Workflow Extensions right from Jira's top Apps menu. Or you can quickly access the Overview page by simply typing gg from any Jira page or by navigating to it through the Apps Admin section.

New features: 

• New libraries:

  • Shared Actions 

  • Scheduled Actions

• New post-functions:

  • Shared Action post-function 

  • Sequence of Post-Functions

  • Display Message to User

Other new features and improvements

• New fieldHistory Nunjucks filter that returns the change history of a field

• New previousStatus Nunjucks filter that returns the previous status of an issue, if any

• A message (in the form of a "flag" at the top-right of the screen) is now displayed on the issue view when an error occurs during the execution of a post-function and the current user is an admin

• The automatic issue view update feature at the end of a transition is now fully compatible with Jira Cloud's "new issue view"

• Nunjucks templates and Jira expressions in transition conditions, validators and post functions tabs are now displayed using a full-featured code viewer

• Group and project role membership can now be tested in Conditions and Validators (build-your-own, conditional validation, ...)

Bug fixes

• [MWEC-472] - Transition History panel doesn't show all transitions if there are more than 100 field changes (Status or other) in issue history

• [MWEC-473] - Assign to last role member post-function doesn't work if last matching role member is too far in the issue history

• [MWEC-475] - Nunjucks Tester is broken in IE 11

• [MWEC-476] - For some errors, the error is logged in Loggly but post function success is logged as well

• [MWEC-478] - Field Required Validator configuration doesn't offer all eligible fields

• [MWEC-479] - Setting the Sprint field to an empty value throws an error

• [MWEC-480] - Error not logged when the Sprint field is set with a string

• [MWEC-483] - Field Required Validator considers a numeric field with value 0 as EMPTY

• [MWEC-486] - Nunjucks/Jira expressions help: examples for testing a field value are incorrect