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

<span style="color: #000000">JMWE 6.2.0 </span><span style="color: #000000">brings the following improvements:</span>

# <span style="color: #000000">New Transitions Activity Tab</span>

<span style="color: #000000">A new Transitions tab is now available under the </span>*<span style="color: #000000">Activity</span>*<span style="color: #000000"> section of the issue view screen. It shows all past transitions, including, whenever possible, the </span>*<span style="color: #000000">name of the transition</span>*<span style="color: #000000"> that was triggered. It even shows "auto-transitions", i.e. transitions that don't change the Status of the issue.</span>

![image](media://df001a1c-9906-4485-b34d-42dd8625cd69)

<span style="color: #000000">Note that this tab can be disabled for all users on the JMWE Configuration page.</span>

# <span style="color: #172b4d">Shared Groovy scripts</span>

You can now create shared Groovy scripts (classes) that can be used from any Groovy script or template from any JMWE workflow condition, validator or post-function. This is really useful for reusing complex logic across multiple workflow transitions.

See the [documentation](https://appfire.atlassian.net/wiki/x/xAynB) for details.

# Conditions, Validators, and Post-functions that worked on linked issues now work on *related* issues

All the JMWE workflow extensions that worked on *linked issues* now work on *related issues* instead. This means that they can now be configured to work on regular linked issues, parent and sub-tasks, Epics and Stories, the Jira Portfolio hierarchy, and even on issues returned by a JQL search or a Groovy expression.

The following workflow extensions are affected and have been renamed accordingly:

- <span style="color: #333333">Linked Issues Condition → Related Issues Condition</span>
- <span style="color: #333333">Linked Issues Status Condition → Related Issues Status Condition</span>
- <span style="color: #333333">Linked Issues Validator → Related Issues </span><span style="color: #333333">Validator</span>
- <span style="color: #333333">Linked Issues Status </span><span style="color: #333333">Validator</span><span style="color: #333333"> → Related Issues Status </span><span style="color: #333333">Validator</span>
- <span style="color: #333333">Clear field(s) of linked issues → </span><span style="color: #333333">Clear field(s) of related issues</span>
- <span style="color: #333333">Comment linked issues</span><span style="color: #333333"> → </span><span style="color: #333333">Comment related issues</span>
- <span style="color: #333333">Copy field value from linked issues</span><span style="color: #333333"> → </span><span style="color: #333333">Copy field value from related issues</span>
- <span style="color: #333333">Copy field value to linked issues</span> → <span style="color: #333333">Copy field value to related issues</span>
- <span style="color: #333333">Set field value of linked issues</span> → <span style="color: #333333">Set field value of related issues</span>
- <span style="color: #333333">Transition linked issues</span> → <span style="color: #333333">Transition related issues</span>

# <span style="color: #172b4d">Configuration Manager support</span>

<span style="color: #172b4d">JMWE now supports the Configuration Manager app from Botron Software. This means that you will be able to use Configuration Manager to move workflows containing JMWE conditions, validators and post-functions from one Jira instance to another with only minimal effort (see the </span>[<span style="color: #172b4d">documentation</span>](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/462095092)<span style="color: #172b4d"> for limitations).</span>

# <span style="color: #172b4d">Groovy improvements</span>

- <span style="color: #172b4d">New </span>`addRemoteIssueLink`<span style="color: #172b4d"> method on the </span>`Issue`<span style="color: #172b4d"> interface to add remote links to an issue</span>
- <span style="color: #172b4d">New </span>`bodyHtml` attribute on the `Comment` interface that returns an HTML-rendered version of the comment body, which is essential when inserting a comment in the HTML body of the Email Issue post-function
- <span style="color: #172b4d">The </span>`linkIssue`<span style="color: #172b4d"> and </span>`getLinkedIssues`<span style="color: #172b4d"> methods of the </span>`Issue`<span style="color: #172b4d"> interface can now take a link type ID and direction (inward or outward) instead of a link type </span>*<span style="color: #172b4d">direction</span>*
- <span style="color: #172b4d">New </span>`getIssueLinks`<span style="color: #172b4d"> method on the </span>`Issue`<span style="color: #172b4d"> interface that returns issue links of the issue in a format compatible with setting the Linked Issues field</span>
- <span style="color: #172b4d">Groovy scripts and templates are now displayed in a more useful way on the condition, validator, and post-function tabs of a transition</span>

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

- <span style="color: #172b4d">"symmetric" link types (which have the same name in both </span>*<span style="color: #172b4d">directions</span>*<span style="color: #172b4d">), such as "relates to", are now treated as one link direction instead of two</span>
- <span style="color: #172b4d">Create issue post-function: use an issue picker instead of a text field for the Parent Issue option</span>
- <span style="color: #172b4d">The Set Field Value of Related Issues and Copy Field Value to Related Issues post-functions now support an option to disable issue notifications</span>

# And a few bug fixes

- [JMWE-760](https://appfire.atlassian.net/browse/JMWE-760)] - Typo in Transition picker
- [[JMWE-761](https://appfire.atlassian.net/browse/JMWE-761)] - Changing the issue type or status field should record the workflow change in the issue history
- [[JMWE-770](https://appfire.atlassian.net/browse/JMWE-770)] - NullPointerException when trying to copy a option value to a project for which the field is not defined (no matching field config scheme)
- [[JMWE-772](https://appfire.atlassian.net/browse/JMWE-772)] - Asterisk missing when the Tempo Account field is made mandatory using the Fields Required Validator
- [[JMWE-776](https://appfire.atlassian.net/browse/JMWE-776)] - Invalid status displayed when using post function creating an auto transition loop in Transition Linked/Parent Issue post-functions
- [[JMWE-779](https://appfire.atlassian.net/browse/JMWE-779)] - Create missing values option gets enabled based on the Source field and not the Destination field
- [[JMWE-780](https://appfire.atlassian.net/browse/JMWE-780)] - Field Required Validator doesn't display error message in JSD projects for the Comment field
- [[JMWE-781](https://appfire.atlassian.net/browse/JMWE-781)] - Linked issues are not fetched in the tester for portfolio link types
- [[JMWE-782](https://appfire.atlassian.net/browse/JMWE-782)] - "Legacy" Portfolio Parent-Child Link type is not supported anymore
- [[JMWE-787](https://appfire.atlassian.net/browse/JMWE-787)] - Setting the Customer Request Type field by name doesn't work reliably when more than 100 request types exist
- [[JMWE-792](https://appfire.atlassian.net/browse/JMWE-792)] - Create/Clone issue(s) If "Iterator" text is longer, then it goes out of the frame in the list of post-function screen. Tested on Chrome (Version 77), Firefox (Version 69) and IE (Version 11) browser.
- [[JMWE-795](https://appfire.atlassian.net/browse/JMWE-795)] - Expected value is incorrect for the Account field of Tempo add-on
- [[JMWE-798](https://appfire.atlassian.net/browse/JMWE-798)] - Copy field value from related issues fails for a multi-valued field when the field is empty for one of the linked issues

- [[JMWE-802](https://appfire.atlassian.net/browse/JMWE-802)] - Conditional validation not saved in "Field has single value" Validator
- [[JMWE-810](https://appfire.atlassian.net/browse/JMWE-810)] - Scripted Validator: doesn't handle GString as return value
- [[JMWE-806](https://appfire.atlassian.net/browse/JMWE-806)] - Copy value from field to field fails when trying to append values to a custom multi version picker field
- [[JMWE-804](https://appfire.atlassian.net/browse/JMWE-804)] - Copy post-functions don't offer Comment as a "from" field anymore
- [[JMWE-805](https://appfire.atlassian.net/browse/JMWE-805)] - Run as user is not obeyed when Comment is copied/set from another field