JMWE 6.5.0 brings the following new features, improvements and bug fixes:

...

New User Condition and Validator

A new User Condition makes a transition available if the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc. Likewise, a new User Validator can validate that the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc.

Image Added

The Create/Clone Issue post-function is now more powerful than ever

The Create/Clone Issue post-function

...

includes new useful options:

• it can automatically copy all fields of the current issue to the new issue(s) - you don't need to specify them one by one anymore
• it can automatically

...

• copy all sub-tasks of the current issue to the new issue(s)
• it saves all newly created issues in the transientVars.newIssues Groovy variable

...

Bug fixes

...

• , so that further post-functions can easily refer to them

Other improvements

• The Email Issue post-function now allows overriding the From and Reply-to names and email addresses

• In the Email Issue post-function, you can now insert the recipient's name and email address into the email subject and body, using the recipient Groovy global variable
• The Display message to user post-function now works on the Create transition
• The getRoleMembers() method of Project objects now only returns active role members, thus eliminating users that have been deactivated

Bug fixes

• JMWE-928 "Show details" dialog box can never be closed on Jira 8.13+
• JMWE-917 Secure Fields fields are not accessible during the Create transition
• JMWE-914 "Run as" field isn't displaying properly on Jira 8.13+
• JMWE-902 Related Issues Validator should display the error message under the Issue Linking field