JMWE for Jira Cloud 1.2.11-AC release notes

This version introduces major new features, some improvements, and bug fixes.

New features

  • Use our new Copy issue fields post-function
    Looking for a powerful post function that copies field value(s) between issues or fields? Look no more! Our new Copy issue fields post-function is here, and it allows you to copy the value(s) of one or more fields from different source issues to those issues that suit your business needs. Be it the current issue or linked issue(s) or a set of issues based on Nunjucks template (or others), this post-function makes copying field(s) from the specified source to target issue(s) simple and easy.
    Here is a quick view of the post-function:

Copy issue fields post-function combines all the features provided by some of the obsolete post-functions (listed in Important information) and offers additional functionality for you to make use of.

  • Mandate a comment during transition using our new Comment Required Validator
    Add the Comment Required Validator to your workflow transition to make it mandatory for the user to enter a comment while transitioning an issue. You can customize an error message to be displayed if the Comment field is left blank during the transition. You can also add conditional validation using Jira expressions to validate a transition for specific scenarios.

  • Set multiple field values using the Set issue fields post-function
    The ability to set more than one field value in one go using the Set issue fields post-function is now available making the job quicker for you. You no longer have to use the post-function multiple times to set multiple field values.

‘Set field value’ post-function is now renamed to Set issue fields.

Improvements

  • Add a post-creation script while using the Create Issue(s) post-function. This allows you to run a Nunjucks script for any additional changes after issue(s) creation.

  • Enable or disable a scheduled action using the newly added toggle in the Scheduled actions page

Important information

We recommend you to take advantage of the post-functions listed in the following table since they are more versatile over some of the obsolete post-functions of similar functionality:

Recommended post-functions

Obsolete post-functions

Bug fixes