Version history
CloudJira Cloud2018-02-22Minor version update 5.2.1Jira Server 6.4 - 7.9.02018-03-22Bug fix release Bug fix:
- [JMWE-618] - NullPointerException in Transition Parent Issue and Transition Linked Issues post-functions in certain cases
5.2.0Jira Server 6.4 - 7.8.22018-03-10Support for transition screens, plus a few other things New Features:
- The Transition Issue, Transition Parent Issue and Transition Linked Issues post-functions now support passing values to the transition screen of the triggered transition
- The issue.get and issue.getAsString methods now support an optional second parameter to specify the value to return if the field is empty
Bug fixes:
5.1.1Jira Server 6.4 - 7.8.22018-02-12Bug fix, two new features 5.1.0Jira Server 6.4 - 7.7.22018-01-25New features, enhancements and bug fixes Full release notes are available here.
New Features:
In Groovy scripts, you can now easily import (use) any Class or Component/Service exposed by Jira or any add-on installed in your Jira instance. You can also use the new issue.getAsJsonData("Field name") method to access a JSON-style version of a field's value.
You can now disable (hide) a global transition from certain issue statuses using the new Current Status Condition.
The Email Issue post-function now supports sending an email to arbitrary email addresses.
Any field made required by the Field is Required Validator will now be marked as required (using a red asterisk) on the corresponding transition or create issue screen.
Improvements:
- Support copying the "attachments" field
- Calculated "Transition" in "Transition XXX issues" post-functions
- Support selecting multiple statuses in the Previous Status condition
- Conditional execution scripts and Scripted Conditions/Validators now support returning Groovy "truth"
...and bug fixes.
5.0.6Jira Server 6.4 - 7.7.22017-11-08Bug fix release Bug fix:
- [JMWE-571] - Post-functions that operate on issue links cannot be created/edited without Jira Software running
5.0.5Jira Server 6.4 - 7.5.42017-10-27New features, enhancements and bug fixes New Features:
- New jqlSearch Groovy function for searching for issues using JQL
- New getRemoteLinks Issue method to access remote links from Groovy scripts
Improvements:
- Inject the transientVars variable into the Groovy context
- Display Groovy expression in the description of post-functions in the list of post-functions
- Provide a summary field for Scripted Conditions and Validators
- Support a customized validation error message in the Parent status validator and Previous status Validator
- Support the Watchers custom field type
- Support Jira Portfolio's "Parent Link" as a link type
Bug fixes:
- Email Issue post-function now doesn't send multiple emails to the same recipient when a user is in multiple roles of the issue
- Cannot add more than one Transition issue post-function to a transition
- Transition picker now works when the workflow name has a "\" or "/"
- Run As now works in Create Issue post-function
- Made Groovy JSON and XML parsers available again
- Resolution field can be cleared
5.0.4Jira Server 6.4 - 7.5.42017-09-11Bug fix release Bug fix:
- [JMWE-549] - Old-style workflow definitions cause NPE in most post-functions
5.0.3Jira Server 6.4 - 7.5.42017-09-06Bug fix Bug fix:
- [JMWE-548] - Post-functions that set a field during the Create transition make Clone operations fail
5.0.2Jira Server 6.4 - 7.4.62017-08-30Bug fixes Bug fixes:
- [JMWE-534] - Comment Issue and Comment Linked Issues post-functions throw an exception when the comment text is null
- [JMWE-536] - ${} annotations in String literals of Groovy scripts are not supported in post-functions
- [JMWE-539] - Errors during Transition Linked/Parent Issues post-functions are not displayed when "Make transitions fail when an error occurs in a JMWE post-function option" is set
- [JMWE-541] - Option values with leading or trailing spaces cannot be set or copied by post-functions
- [JMWE-543] - Groovy editor is still displayed even when a field is being set using Set field value to constant
- [JMWE-544] - On-the-fly Groovy syntax checking does not work anymore
- [JMWE-545] - Field is required validator doesn't support the Issue Links field
- [JMWE-546] - Any post-function that sets/copies the Watchers on the current issue prevents the new Watchers from being removed
- [JMWE-547] - Groovy errors are not cleared from the Groovy editor when the value type is changed
5.0.1Jira Server 6.4 - 7.4.62017-08-11Minor bug fixes Enhancement:
- The "Field is Required" validator now supports the "Attachment" field
Bug fixes:
5.0.0.1Jira Server 6.4 - 7.4.62017-07-12JMWE 5.0, our biggest release ever! We are excited to announce JMWE 5.0, our biggest release ever! In this release, we've added a few key features and made JMWE much easier to use.
Some highlights:
- Completely redesigned configuration screens - it is now much easier to configure JMWE conditions, validators, and post-functions, with more detailed explanations, direct access to documentation, and more intuitive controls.
- Groovy editor and tester - you can now write Groovy scripts in a full-featured editor, complete with syntax highlighting, syntax check and integrated script tester.
- New documentation - we've completely rewritten the product documentation.
- New post-functions - create/clone issues, send custom issue notification emails, and link and unlink issues directly from a workflow transition.
- Linked issue status condition and validator - control the execution of the post-function based on the status of linked issues, such as Stories of an Epic or the Epic of a Story
- And 50+ smaller improvements and bug fixes...
5.0.0Jira Server 6.4 - 7.4.62017-07-11JMWE 5.0, our biggest release ever! We are excited to announce JMWE 5.0, our biggest release ever! In this release, we've added a few key features and made JMWE much easier to use.
Some highlights:
- Completely redesigned configuration screens - it is now much easier to configure JMWE conditions, validators, and post-functions, with more detailed explanations, direct access to documentation, and more intuitive controls.
- Groovy editor and tester - you can now write Groovy scripts in a full-featured editor, complete with syntax highlighting, syntax check and integrated script tester.
- New documentation - we've completely rewritten the product documentation.
- New post-functions - create/clone issues, send custom issue notification emails, and link and unlink issues directly from a workflow transition.
- Linked issue status condition and validator - control the execution of the post-function based on the status of linked issues, such as Stories of an Epic or the Epic of a Story
- And 50+ smaller improvements and bug fixes...
4.0.7Jira Server 6.4 - 7.4.62017-02-16Minor bug fixes Bug fixes:
4.0.6Jira Server 6.4 - 7.3.92016-12-13Minor bug fixes Bug fixes:
4.0.5Jira Server 6.4 - 7.2.132016-09-23Bug fixes. Bug fixes:
4.0.4Jira Server 6.4 - 7.2.132016-05-26New features, bug fixes New Features
Improvement
- [JMWE-404] - Support "Include Current Status" option in Previous Status condition
Bug fixes
- [JMWE-405] - Transition Issue cancels the current transition when a Condition blocks the transition
- [JMWE-409] - Help text for "Assign to last role member" options is wrong
- [JMWE-411] - Field Required Validator doesn't work for the Issue Links field during the Create transition
- [JMWE-414] - List of statuses displayed in the Previous status validator
4.0.3Jira Server 6.4 - 7.1.102016-02-26Bug fixes 4.0.2Jira Server 6.4 - 7.1.102015-11-04Major bug fixes Bug fixes:
4.0.1Jira Server 6.4 - 7.0.112015-10-23Minor bug fix Bug fix:
- [JMWE-394] - [Regression] Cannot set watchers from post-function
4.0.0Jira Server 6.4 - 7.0.112015-10-18Jira 6.4 and 7 support This release supports Jira 6.4 and Jira 7.0 and above.
4.0.0-Beta8Jira Server 7.0.0 - 7.0.112015-10-06Jira 7 compatibility Version 4.0.0-Beta8 • Released 2015-10-06 • Supported By Innovalog • Paid via Atlassian • CommercialThis version provides compatibility with Jira 7 (JMWE-338). Please note that, because of major API changes in Jira 7, JMWE 4.0.0 and above will only work with Jira 7 and above. For Jira 5 and Jira 6, please use the latest 3.x version instead.
In addition, this version brings the following changes:
Improvement:
- [JMWE-347] - Support comment visibility in the Comment [Linked] Issue post-function(s)
Bug fixes:
3.7.2Jira Server 5.1 - 6.4.142016-02-26Minor bug fixes 3.7.1Jira Server 5.0 - 6.4.142015-09-22Bug fix This release includes a single bug fix:
- [JMWE-380] - AssignToLastRoleMember doesn't work with some users
3.7.0Jira Server 5.0 - 6.4.142015-09-16Various improvements and bug fixes New Feature:
- [JMWE-324] - Ability to run post-functions that affect other issues as a different user (for Jira Service Desk)
Improvement:
- [JMWE-332] - issue.get() should support identifying custom fields by their name
Bug fixes:
- [JMWE-328] - Assign to last role member: Use selected assignee option doesn't create entry in issue history
- [JMWE-331] - Post-functions that operate on linked issues stop at the first condition that returns false
- [JMWE-371] - Setting the Issue Security Level field from a String should take issue's Security Scheme into account
3.6.1Jira Server 5.0 - 6.4.142015-05-02Minor improvements and bug fixes 3.6.0Jira Server 5.0 - 6.4.142015-03-09New features and bug fixes 3.5.2Jira Server 5.0 - 6.3.152014-10-05New post-function, bug fixes 3.5.1Jira Server 5.0 - 6.3.152014-07-19Fixed uninstallation / upgrade issue This release works around a major issue when upgrading or uninstalling plugins, caused by a bug in Jira prior to 6.3.
WARNING: some Groovy scripts used in post-functions might stop working, because some Java packages will become unavailable.
3.5.0Jira Server 5.0 - 6.3.152014-07-17Jira Data Center compatibility,bug fixes 3.3.2Jira Server 5.0 - 6.3.152014-07-15Minor bug fixes and improvements WARNING: this release replace version 3.3.1, which included a regression on the Transition Parent Issue and Transition Linked Issues functions.
Bug fixes:
- [JMWE-223] - Parent Status Validator message is broken
- [JMWE-226] - Cannot copy cascading select custom field values
- [JMWE-227] - Assign to inactive user bug in "Assign to last role member" post function
- [JMWE-236] - Transition linked issue does not work if several transitions have the same name
- [JMWE-243] - Unknown Exception in CommentRequiredValidator
- [JMWE-244] - Transition Parent Issue post-function is broken
Improvements:
- [JMWE-241] - "Issue Commented" event for the Comment Postfunction
- [JMWE-224] - Make all packages in the OSGi context available from Groovy scripts
3.3.0Jira Server 5.0 - 6.2.72014-02-06Minor enhancements and bug fixes New in this release
Fixed in this release
- [JMWE-124] - Comment Required Validator - Not able to add comment in Bulk Changes
- [JMWE-183] - A role which was used in a post function has been removed, and now we cannot remove the post function which referenced that role
- [JMWE-209] - Configure page should state it is not useful when using UPM 2.0.1+
- [JMWE-210] - "Set Field Value from Linked Issue" function doesn't support "Issue type" field
- [JMWE-221] - Assign to last role member does not work properly after upgrading to Jira 6+
3.2.0Jira Server 5.0 - 6.1.92013-10-28New features and bug fixes New in this release
Fixed in this release
- [JMWE-111], [JMWE-162], [JMWE-193] Support Watchers field
- [JMWE-191] Set Field Value function does not support arrays of strings
- [JMWE-194] Support adding field values in Set Field Value and similar post-functions
- [JMWE-202], [JMWE-204] Fix issue with user fields
- [JMWE-206] Separation of duties partially broken
3.1.1Jira Server 5.0 - 6.1.92013-09-13Minor enhancements, bug fix 3.1.0Jira Server 5.0 - 6.0.82013-08-17New post-functions, bug fixes Bug
- [JMWE-182] - "Copy Value From Field to Field" does not copy parent value from cascading select list
Improvement
- [JMWE-178] - "Copy Value From Field to Field" post-function does not allow copying just the Parent value
New Feature
- [JMWE-177] - Set Field Value of Linked Issues Post-function (incl. Epic/Issue links)
- [JMWE-180] - Set Field Value to constant or Groovy expression Post-Function
3.0.1Jira Server 5.0 - 6.0.82013-07-10Minor enhancements Bug fixes / improvements
- [JMWE-173] - Assign to role member Function - skip Assignee option not working as expected
- [JMWE-176] - Trouble with assignments during transition
Note to OnDemand users
Jira Misc Workflow Extensions became "paid-via-Atlassian" for on-premise Jira in May (see the 3.0.0 release notes). It will become "paid-via-Atlassian" for OnDemand customers in August. If you do not wish to continue using JMWE, you will then be able to request a free evaluation license to give you time to remove your dependency on the plugin.3.0.0Jira Server 5.0 - 6.0.82013-05-31Jira 6 compatibility, new post-functions Improvements
This version brings Jira 6 compatibility, as well as a new set of post-functions that allow you to copy field values between linked issues, including between GreenHopper Epics and their associated issues.
- [JMWE-157] - Jira 6 compatibility
- [JMWE-164] - Set field values from/to linked issues (or Issues and Epics)
Bug fixes
- [JMWE-16] - Copy Field Value to Parent (CopyFieldValueToParent-function) does not trigger Parent re-index post function on Jira 5.1 and above
- [JMWE-79] - "Cascading Select" custom fields not compatible with "Set Field Value from Parent" post function
- [JMWE-169] - Receiving com.atlassian.jira.issue.customfields.view.CustomFieldParamsImpl cannot be cast to java.util.Map error when trying to use "Set Field Value from Parent Function" post function
Licensing change
After five years of free availability, we have decided to move this plugin to the "pay-via-Atlassian" model. The main driver behind this decision, which we'd been postponing for more than a year, is the vastly increased level of support we have had to provide to our users, as well as the investment we had to make to port the plugin to Jira 6 (which introduced major API changes).We believe, and hope, that the price we've set, around 10% of the price of a Jira license, will be acceptable for most of our faithful users.
2.5.7.1Jira Server 5.0 - 5.2.112013-03-22Fix compatibility with Jira 5.0.x JMWE-163 Fixed compatibility with Jira 5.0.x
2.5.7Jira Server 5.0 - 5.2.112013-03-19Minor improvement 2.5.6Jira Server 5.0 - 5.2.112013-03-192 bug fixes 2.5.5.2Jira Server 5.0 - 5.2.112013-03-13Minor bug fixes Bug
- [JMWE-127] - Can not copy value from user's property to 'Component/s' field
- [JMWE-148] - Logging is broken
- [JMWE-149] - Copy From Field To Field post-function doesn't handle multi-user-picker fields properly
- [JMWE-153] - Copy Value from Other Field fails when using Cascade Select custom Field
Improvement
- [JMWE-154] - Post function " Copy Field Values to another Field" does not copy the first level of Cascade Select
2.5.4Jira Server 5.0 - 5.2.112012-11-20Minor bug and security fixes Bug
- [JMWE-71] - Warnings "There are no users assigned in the project role..." in atlassian-jira.log
- [JMWE-133] - XSS vulnerabilities present in most workflow conditions, validators and post functions
- [JMWE-129] - previousstatus-condition-view.vm: Multiple Error - Left side ($not) of '==' operation has null value.
Improvement
- [JMWE-145] - PreviousStatusCondition should ignore loop transitions
2.5.2Jira Server 5.0 - 5.1.82012-08-06Jira 5.1 compatibility, minor feature enhancements, minor bug fixes 2.4.4Jira Server 4.4 - 4.4.52012-08-06Minor feature enhancements, minor bug fixes 2.5.1Jira Server 5.0 - 5.0.72011-12-04Minor bug fixes - [ JMWE-95] - upgrading jira 4.2 to 4.4 causes java.lang.UnsupportedOperationException: Not implemented from CopyValueFromOtherFieldPostFunction
- [ JMWE-97] - Comment Required Validator with user group exemption causes unknown exception casting com.atlassian.crowd.embedded.impl.ImmutableGroup to com.opensymphony.user.Group
- [ JMWE-99] - Nullpointer on comment required validator
- [ JMWE-98] - using value before current transition
Tested against Jira 5.0 RC1
2.4.3Jira Server 4.4 - 4.4.52011-12-04Minor bug fixes 2.4.2Jira Server 4.4 - 4.4.52011-11-17Minor bug fixes 2.5.0Jira Server 5.0 - 5.0.72011-10-22Compatibility with Jira 5 Compatibility with Jira 5
2.4.1Jira Server 4.0 - 4.4.52011-03-16In Assign To Last Role Member function, add an option to take current assignee into account [JMWE-67] - In Assign To Last Role Member function, add an option to take current assignee into account
2.4Jira Server 4.0 - 4.3.42011-03-06One new function, several fixes and enhancements Bug
- [JMWE-51] - typo in comments / comments differ from code
- [JMWE-58] - Transition Parent Issue can't handle duplicate names
- [JMWE-61] - Transition Parent Issue
Improvement
- [JMWE-53] - Implement function "Copy field from parent to subissue" upon creation of subissues
New Feature
- [JMWE-59] - Add values to MultiSelect field from other field needed
2.2Jira Server 4.0 - 4.2.42010-10-29Added new "Hide Transition" condition JMWE-46 : new "Hide Transition" condition
The purpose of the Hide Transition workflow condition is to hide a transition from the user, thus preventing the user from triggering it, while making it available to the Transition Parent Issue function or to scripts or remote API calls.
1.5.4Jira Server 3.10.2 - 4.1.22010-08-08Fixing JMWE-28, JMWE-30 and JMWE-35. Fixed the following issues:
JMWE-28 Assign to Role Member fails for project names with non-alphanumeric characters
JMWE-30 Editing "comment required" validator throws error
JMWE-35 AssigntoRoleMember fails when workflow created before "skipifassignee" checkbox was available.
Note: this is the last version compatible with Jira < 4.0 (version ONE type plugin)
1.5.3Jira Server 3.10.2 - 4.1.22010-03-27JMWE-28: improved Assign to role member function JMWE-28: Assign to Role Member function now works with project names containing non-alphanumeric characters, using a new syntax (see documentation)
1.5.2Jira Server 3.10.2 - 4.0.22010-03-18Enhancements to several post-functions JMWE-22: optionally prevent Assign to [last] role member from changing assignee if assignee explicitly set in transition screen
JMWE-25: support the Issue Security field in set field value from user property
JMWE-26: make "Set issue security level based on user's project role" function work in Jira 3.12
1.5.1Jira Server 3.10.2 - 4.0.22010-02-06JMWE-23: consider reporter in "Assign to last role member" function JMWE-23: consider reporter in "Assign to last role member" function
1.5Jira Server 3.10.2 - 4.0.22009-10-24Added SetIssueSecurityFromRole post-function JMWE-20 : added Set issue security from user role post-function
1.4Jira Server 3.10.2 - 4.0.22009-09-02Compatibility with Jira 4 JMWE-17: add compatibility with Jira 4
1.3.3Jira Server 3.10.2 - 3.13.42009-08-28Fixed JMWE-16 Fixed JMWE-16: parent issue was not indexed properly during Copy/Add field value to Parent issue.
1.3.2Jira Server 3.10.2 - 3.13.42009-07-08New Copy Field Value to Parent function JMWE-14: Added a "Copy Field Value to Parent" post function
1.3.1Jira Server 3.10.2 - 3.13.42009-06-19Fixed JMWE-11 Fixed JMWE-11: allow selected groups to bypass Comment Required validator (for bulk transitions)
1.3Jira Server 3.10.2 - 3.13.42009-04-27New Field Changed Validator Implemented JMWE-10 : New Field Changed validator
Fixed JMWE-8: disable Comment Required validator during SOAP calls to progressWorkflowAction
1.2.3Jira Server 3.10.2 - 3.13.42009-02-05Released on 2009-02-05 Fixed JMWE-4 : Set field value from User Property value Function does not work with multi-valued custom fields
1.2.2Jira Server 3.10.2 - 3.13.42009-02-01Released on 2009-02-01 Fixed JMWE-3 (Set field value from User Property value Function only works with a destination field of type User).
1.2.1Jira Server 3.10.2 - 3.13.42009-01-05Released on 2009-01-05 Fixed JMWE-2 (a bug in Add Field Value to Parent Function).
1.2Jira Server 3.13 - 3.13.42008-12-09Released on 2008-12-09 Added Assign To Role Member workflow functions (from Stanislav Laufik's plugin).
1.1Jira Server 3.13 - 3.13.42008-11-29Released on 2008-11-29 Added Separation of Duties Condition.
1.0Jira Server 3.13 - 3.13.42008-11-23Released on 2008-11-23 Initial release