---
title: "JMWE for Jira Server 6.3.0 release notes"
canonical: "https://support.appfire.com/space/JMWE/461472396/JMWE%20for%20Jira%20Server%206.3.0%20release%20notes"
format: markdown
---
> Macro (aura-html)

<span style="color: #333333">JMWE 6.3.0 brings the following new features and improvements:</span>

# <span style="color: #333333">Send attachments using the Email Issue post-function</span>  


<span style="color: #333333">The </span>[<span style="color: #333333">Email Issue post-function</span>](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461767713)<span style="color: #333333"> can now add issue attachments to the notification email. You can include all the attachments of the issue, only the attachments added on the transition screen, or even attachments from other issues.</span>

![image](media://07a6fc8f-0aec-45c1-a296-aec2b8ab6545)

*<span style="color: #333333">Bonus feature:</span>*<span style="color: #333333"> inline images in the email body will also be attached to the notification email and will appear within the email body. </span>

# <span style="color: #333333">New </span>*<span style="color: #333333">Return to Previous Status</span>*<span style="color: #333333"> post-function: go back to the previous status of an issue</span>

<span style="color: #333333">In cases when multiple transitions lead to the same status (e.g. Escalated), you can use </span>[<span style="color: #333333">this new post-function</span>](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461570592)<span style="color: #333333"> to return the issue to the previous status. </span>

# <span style="color: #333333">New </span>*<span style="color: #333333">Display Message to User</span>*<span style="color: #333333"> post-function: showing custom messages on transition</span>

<span style="color: #333333">Use the new </span>[<span style="color: #333333">Display Message to User post-function</span>](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461963840)<span style="color: #333333"> 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. </span>

![image](media://ebdd1b2d-a062-4d20-a765-d7a2b1f78552)

<span style="color: #333333">A new </span>`showMessageToUser()`<span style="color: #333333"> method is also available on the </span>`Issue`<span style="color: #333333"> interface to send a message to the user.</span>

# <span style="color: #333333">The Transitions tab can now be displayed conditionally</span>

<span style="color: #333333">You can now control </span>**<span style="color: #333333">who</span>**<span style="color: #333333"> can see the </span>[<span style="color: #333333">Transition activity tab</span>](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461472022)<span style="color: #333333"> on the issue view, and o</span><span style="color: #333333">n which </span>**<span style="color: #333333">issues/projects</span>**<span style="color: #333333"> it will be displayed.</span>

# <span style="color: #333333">Post-function errors are now displayed to administrators</span>

<span style="color: #333333">Whenever an error occurs during the execution of a JMWE post-function, and the transition was triggered by a Jira administrator, a message is displayed in the top-right corner of the page to help identify and troubleshoot misconfigured post-functions. </span>

<span style="color: #333333">Note that this message is only displayed if the post-function is </span>**<span style="color: #333333">not</span>**<span style="color: #333333"> configured to </span>*<span style="color: #333333">fail</span>*<span style="color: #333333"> (and stop the transition from completing) when an error occurs.</span>

# <span style="color: #333333">New REST API to import/export shared Groovy scripts</span>

A new REST API allows you to export individual shared scripts or all scripts at once, import new or updated shared scripts, and delete shared scripts.

# <span style="color: #333333">Other improvements</span>

- Shared scripts can now be migrated using [Botron Configuration Manager](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/462095092)
- Fields of unsupported field types implemented by third-party apps can now be copied by post-function that copy fields
- The Link Issues post-function now offers a "real" Conditional Execution option in addition to a filter for the issues returned by the JQL search expression
- The Set field value from User Property post-function now allows selecting the user whose property should be read
- The Related Issues Condition, Related Issue Status Condition, and corresponding Validators now offer "negative" conditions (e.g. issue has *no* linked issues of a certain type)
- The Related Issues Status Condition and Validator can now check whether *all* or *at least one* related issue(s) are in the selected Statuses
- Groovy scripts now throw an error when attempting to modify certain Jira objects such as Status, Priority, etc. (which usually happens when inadvertently using "=" instead of "==" in a comparison)
- The Transition Picker now offers an option to not add the workflow name
- The Field Required validator will now show the red asterisk if the *initial* evaluation of the conditional execution script returns true (before the transition screen is displayed)
- You can now explicitly exclude recipients in the Email Issue post-function
- The `getComponent()` global function can now return *private* components (services) of other apps

# And bug fixes

- [[JMWE-830](https://appfire.atlassian.net/browse/JMWE-830)] - Incorrect Customer Request Type interface in the Groovy editor
- [[JMWE-831](https://appfire.atlassian.net/browse/JMWE-831)] - Fix example in the Expected Value tab for a date picker field
- [[JMWE-836](https://appfire.atlassian.net/browse/JMWE-836)] - Setting the Customer Request Type field by name doesn't work reliably when more than 100 request types exist on JSD 3
- [[JMWE-838](https://appfire.atlassian.net/browse/JMWE-838)] - java.lang.NoClassDefFoundError exception while testing a Groovy script
- [[JMWE-839](https://appfire.atlassian.net/browse/JMWE-839)] - Some shared script errors can break every other JMWE Groovy script
- [[JMWE-840](https://appfire.atlassian.net/browse/JMWE-840)] - Related Issues: Groovy: Code after colon gets truncated under source issues
- [[JMWE-843](https://appfire.atlassian.net/browse/JMWE-843)] - Transitions tab: transition date/time is not displayed in the same time zone as the history tab
- [[JMWE-849](https://appfire.atlassian.net/browse/JMWE-849)] - Related Issues Status Validator doesn't take into account issue links being added during the transition
- [[JMWE-850](https://appfire.atlassian.net/browse/JMWE-850)] - Related Issues Validator: the Check related issues option doesn't work when no such related issue exists
- [[JMWE-851](https://appfire.atlassian.net/browse/JMWE-851)] - Transitions tab can throw an error if a custom field named "status" exists