The highly-anticipated Jira Misc Workflow Extensions (JMWE) 6.2 is here, and we are excited to let you know about a few important new features, as well as many improvements.

JMWE is focused on offering a diverse feature set to help you automate your Jira workflows. Many no-code point-and-click workflow extensions, plus an ability to extend even further with Groovy scripting, let you do more with Jira. 

• New transition Activity tab for end-users
• Shared Groovy Scripts feature for faster scripting
• Supercharged code-free extensions
• A better way of moving workflows from testing to development

1: NEW TRANSITION ACTIVITY TAB

[FOR JIRA USERS]​

Jira users can now see the complete transition history of an issue

Previously available only in JMWE for Jira Cloud, the Transitions history tab has been released in JMWE for Jira Server and Data Center. Now, users can easily see all previous status transitions, when and by whom they were triggered, the time in status, all in one list. For example, it will help users understand who submitted feature specifications and when, who coded the feature, who tested it, and how long it took.

Users can find JMWE Transition tab in the Activity section of the Issue View screen, under "Transitions" and view the following information:​

• To and From statuses of transitions, in chronological order;
• The name of the transition that was triggered (whenever possible);
• Auto-transitions (transitions that don't change the status of the issue);
• When the transition was triggered;
• Author of the transition;
• Time in Status - how long the issue spent in the original "from" status (left of the arrow) before being transitioned.

The JMWE Transitions tab is enabled by default, but you can also turn it off to remove it from user views. If you choose to hide the JMWE's Transition tab, uncheck the option on the configuration page.

2: SHARED GROOVY SCRIPTS

[FOR SCRIPTING OPTIONS] 

Reuse Groovy scripts in workflows

​We now have a super useful feature - Shared Groovy Scripts - to help Admins simplify and speed up scripting by reusing complex logic across multiple workflow transitions. You can create shared Groovy scripts (classes) that can be used from any Groovy script or template, from any JMWE workflow condition, validator, or post-function.

For example, you can create a shared script to use in a post-function that will add a certain number of days to a date, excluding weekends. Or create a script that checks whether attachments of a specified type were added on the transition screen.

You can access the "Shared Groovy Scripts" library from the admin section of JMWE. There, you can create new shared scripts, view the library of existing scripts to edit and delete them.

See the documentation for more details.

More on Groovy:

We never stop working on improving the way Groovy fans can use scripting in JMWE. There are several Groovy improvements in this release - take a look at the release notes. 

3: RELATED ISSUES EXTENSIONS

[FOR NO-CODE CONFIGURATIONS]   [FOR SCRIPTING OPTIONS] 

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. This improvement not only extends the functionality of these extensions, but it also makes them much clearer and easier to configure.

With this release, these improved extensions can now be configured to work on:

• Regular issue links
• Parent and sub-tasks
• Epics and Stories
• Jira Portfolio hierarchy
• Issues returned by a JQL search (new)
• Issues returned by Groovy expression (new)

See the release notes for the full list of improved - and renamed - workflow extensions.

4: CONFIGURATION MANAGER SUPPORT

[FOR JIRA ADMINISTRATION]

Seamless integration with Botron's Configuration Manager

JMWE now supports the Configuration Manager app from Botron Software, a popular enterprise solution for managing Jira configurations at scale. It captures all your Jira configurations and issue data in a self-contained, portable snapshot that can be deployed on any Jira instance, for example, between Test, Staging to Production environments.

You will now 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 documentation for more information and limitations.