Bug fix:

• [JMWE-618] - NullPointerException in Transition Parent Issue and Transition Linked Issues post-functions in certain cases

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:

• [JMWE-609] - Options containing the ß character are now supported
• [JMWE-610] - issue.get and similar methods now lookup fields by localized name as well as English name
• [JMWE-611] - Create Issue post-function doesn't set resolution date anymore when a default Resolution has been defined

New Features:

• [JMWE-597] - New originalIssue variable available to Groovy scripts
• [JMWE-598] - Issue.getFieldHistory method

Bug fix:

• [JMWE-596] - Conditions should refer to the original issue and not the current issue

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.

Bug fix:

• [JMWE-571] - Post-functions that operate on issue links cannot be created/edited without Jira Software running

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

Bug fix:

• [JMWE-549] - Old-style workflow definitions cause NPE in most post-functions

Bug fix:

• [JMWE-548] - Post-functions that set a field during the Create transition make Clone operations fail

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

Enhancement:

• The "Field is Required" validator now supports the "Attachment" field

Bug fixes:

• [JMWE-528] - Add field value(s) option of Copy Field Value From Parent post-function works again
• [JMWE-533] - ${} annotations in Groovy Templates are now supported in post-functions

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...

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...

Bug fixes:

• [JMWE-448] - Post-function that set field values of other issues don't write to history if field is custom
• [JMWE-462] - Reverse Condition of Previous Status Condition not respecting include current status option

Bug fixes:

• [JMWE-444] - Required field validator doesn't support Tempo's Account field
• [JMWE-445] - Post-functions, Validators and Conditions don't support identically-named fields

Bug fixes:

• [JMWE-439] - Append values option doesn't work when source value is null
• [JMWE-440] - Parent Status Validator and Previous Status Validator don't display correct error message

New Features

• [JMWE-313] - Groovy-based Condition
• [JMWE-314] - Groovy-based Validator

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

Bug fixes:

• [JMWE-398] - Setting watchers from post-function is broken in Jira 7
• [JMWE-399] - Cannot copy Project Picker type fields on Jira 6.4
• [JMWE-400] - Issue with setting of value (nFeed) from a linked issue

Improvement:

• [JMWE-401] - Create a more explicit Configure page

Bug fixes:

• [JMWE-395] - Transition Issue post-function does not work after upgrading to Jira 7
• [JMWE-396] - Field is Required Validator not compatible with Jira 7
• [JMWE-397] - Post-function "Assign to last role member" broken on Jira 6

Bug fix:

• [JMWE-394] - [Regression] Cannot set watchers from post-function

This release supports Jira 6.4 and Jira 7.0 and above.

This 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:

• [JMWE-363] - Cannot copy from multi-user custom field to single-user field (custom or system)
• [JMWE-380] - AssignToLastRoleMember doesn't work with some users

Bug fixes

• [JMWE-385] - "Set issue security level based on user's project role" should reject invalid security level
• [JMWE-400] - Issue with setting of value (nFeed) from a linked issue

Improvement

• [JMWE-401] - Create a more explicit Configure page

This release includes a single bug fix:

• [JMWE-380] - AssignToLastRoleMember doesn't work with some users

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

Improvement:

• [JMWE-302] - Previous status condition should optionally recognize auto-transitions

New Feature

• [JMWE-305] - Transition Subtasks Post-function

Bug fixes:

• [JMWE-271] - Transition issue post-function does not work for Create Issue transition
• [JMWE-306] - Copying User values from one field to another fails if User keys are different from User IDs
• [JMWE-321] - [Regression] Copying the Component/s field doesn't work anymore

New Features:

• [JMWE-269] - Make Field Changed Validator work with Issue Links
• [JMWE-277] - Comment Linked Issue post-function

Bug fixes:

• [JMWE-274] - Transition Issue post-functions cannot trigger "common transitions" nor "global transitions"
• [JMWE-296] - Comment issue Function mapping wrong with renamed users

New Feature:

• [JMWE-254] - Add transition issue post-function

Improvement:

• [JMWE-259] - Set Issue Security post-function should show Issue Security Scheme name in combo

Bug fixes:

• [JMWE-220] - Transition Parent Issue: invalid transition causes superfluous logging
• [JMWE-255] - Condition "Hide transition from user" is broken with Jira 6.3
• [JMWE-264] - Required Field Validator does not work with the Issue Links field in Jira 6.3

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.

New Feature:

• [JMWE-245] - Jira Data Center compatibility

Bugs:

• [JMWE-247] - Field has been modified Validator does not work with Time Spent field
• [JMWE-248] - Copy field to field workflow post function not working on select list

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

New Feature

• [JMWE-185] - Transition Linked Issues post-function
• [JMWE-189] - Field Required Validator with custom message

Bug fix

• [JMWE-184] - Invalid Version copied during "Copy Field Value To Linked Issues" post-function when copying across projects

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

• [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

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

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. 

JMWE-163 Fixed compatibility with Jira 5.0.x

Improvement

• [JMWE-109] - Only copy field value from parent if not already set

Bug

• [JMWE-156] - Add Field Value to Parent Function doesn't work with Label fields
• [JMWE-161] - JMWE 2.5.5 not compatible with Jira 5.0-5.1

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

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

Jira 5.1 compatibility.

Bug

• [JMWE-100] - Unable to copy value from user property to field security (Security Level)
• [JMWE-115] - Error with separation of duties finding available actions
• [JMWE-116] - Set field value from parent does not work

Improvement

• [JMWE-83] - Unable to copy labels from parent
• [JMWE-110] - Add a NOT option to the Previous State Condition
• [JMWE-120] - Ability to have "None" as an option in "Set issue security level based on user's project role" post-function

Bug

• [JMWE-100] - Unable to copy value from user property to field security (Security Level)
• [JMWE-115] - Error with separation of duties finding available actions
• [JMWE-116] - Set field value from parent does not work
• [JMWE-83] - Unable to copy labels from parent

Improvement

• [JMWE-110] - Add a NOT option to the Previous State Condition
• [JMWE-120] - Ability to have "None" as an option in "Set issue security level based on user's project role" post-function

• [ 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

• [ 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-92] - crash on adding "comment mandatory" validator
• [ JMWE-95] - upgrading jira 4.2 to 4.4 causes java.lang.UnsupportedOperationException: Not implemented from CopyValueFromOtherFieldPostFunction

Compatibility with Jira 5

[JMWE-67] - In Assign To Last Role Member function, add an option to take current assignee into account

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

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.

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)

JMWE-28: Assign to Role Member function now works with project names containing non-alphanumeric characters, using a new syntax (see documentation)

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

JMWE-23: consider reporter in "Assign to last role member" function

JMWE-20 : added Set issue security from user role post-function

JMWE-17: add compatibility with Jira 4

Fixed JMWE-16: parent issue was not indexed properly during Copy/Add field value to Parent issue.

JMWE-14: Added a "Copy Field Value to Parent" post function

Fixed JMWE-11: allow selected groups to bypass Comment Required validator (for bulk transitions)

Implemented JMWE-10 : New Field Changed validator

Fixed JMWE-8: disable Comment Required validator during SOAP calls to progressWorkflowAction

Fixed JMWE-4 : Set field value from User Property value Function does not work with multi-valued custom fields

Fixed JMWE-3 (Set field value from User Property value Function only works with a destination field of type User).

Fixed JMWE-2 (a bug in Add Field Value to Parent Function).

Added Assign To Role Member workflow functions (from Stanislav Laufik's plugin).

Added Separation of Duties Condition.

Initial release