JMWE for Jira Cloud 1.2.14-AC release notes

This version brings the following changes:

New User Condition and Validator

A new User Condition allows you to hide a particular transition from the list of available workflow actions based on either the current user or users in a specific field meeting certain criteria, such as being the reporter or assignee, belonging to certain groups or project roles, satisfying a Jira expression, etc. See the User Condition documentation page to learn more.

A new User Validator can validate that either the current user or users in a specific field meet certain criteria, such as being the reporter or assignee, belonging to certain groups or project roles, satisfying a Jira expression, etc. See the User Validator documentation page to learn more.

Send errors and/or warnings to a Webhook

You can now configure a Webhook to receive JMWE errors and/or warnings as soon as they happen. See the JMWE logs documentation page to learn more.

Support for Insight Objects custom fields

You can now copy Insight Objects custom fields between issues and between custom fields. You can also set an Insight Objects custom field value using Object IDs. Finally, you can use the new insightFieldValue Nunjucks filter to return the full details of an Insight Objects custom field value in Jira Cloud Premium.

New Overview page

A redesigned Overview page helps you get started with JMWE quickly and then helps you easily navigate through JMWE’s extensive feature set.

Other improvements

• New in & allIn Nunjucks filters to check if any/all values in an array exist in another array.

• Workflow Conditions, Validators, and Post-functions that have been modified on a transition now show an UnpUblished changes indicator if the workflow hasn’t yet been published.

Bug fixes