For more information, please refer to the release notes.
Version history
CloudJira Cloud2023-04-20New features, improved security and bug fixes 8.3.0Jira Server 7.3.0 - 9.8.12023-05-29New features and bugfixes This version includes bugfixes and a new "Set issue fields" post-function, among other improvements.
For the full list of changes, please refer to the full release notes.
8.3.0Jira Data Center 7.3.0 - 9.8.12023-05-29New features and bugfixes This version includes bugfixes and a new "Set issue fields" post-function, among other improvements.
For the full list of changes, please refer to the full release notes.
8.2.0Jira Server 7.3.0 - 9.8.12023-03-02New features, upgrades and bugfixes This version includes bugfixes, upgrades, and a new "Assign issue" post-function, among other improvements.
For the full list of changes, please refer to the full release notes.
8.2.0Jira Data Center 7.3.0 - 9.8.12023-03-02New features, upgrades and bugfixes This version includes bugfixes, upgrades, and a new "Assign issue" post-function, among other improvements.
For the full list of changes, please refer to the full release notes.
8.1.2Jira Server 7.3.0 - 9.6.02022-12-23Bugfixes for shared extensions This version includes bugfixes for shared, event-based and scheduled actions.
For the full list of changes, please refer to the full release notes.
8.1.2Jira Data Center 7.3.0 - 9.6.02022-12-23Bugfixes for shared extensions This version includes bugfixes for shared, event-based and scheduled actions.
For the full list of changes, please refer to the full release notes.
8.1.1Jira Server 7.3.0 - 9.5.12022-12-22Bugfixes and security improvements This version includes updates to libraries which were affected by vulnerabilities and fixes incompatibilities with certain databases.
For the full list of changes, please refer to the full release notes.
8.1.1Jira Data Center 7.3.0 - 9.5.12022-12-22Bugfixes and security improvements This version includes updates to libraries which were affected by vulnerabilities and fixes incompatibilities with certain databases.
For the full list of changes, please refer to the full release notes.
8.1.0Jira Server 7.3.0 - 9.5.12022-12-08Shared conditions and validators, Jira 9.5 compatibility, minor improvements This release introduces Shared conditions and Shared validators, bringing the power of Shared actions to all our workflow extensions.
Other improvements:
- Jira 9.5 compatibility
- REST APIs for shared extensions
- Support using values from before the running transition in "Copy issue fields" post-function
- Added "reverse" option for User condition and User validator
- Bugfixes
- "Transition issue" post-function now uses the specified runAsUser parameter when checking conditions for the specified transition
- Email logs for mails created using "Email issue" post-function now display the full details
For the full list of changes, please refer to the full release notes
8.1.0Jira Data Center 7.3.0 - 9.5.12022-12-08Shared conditions and validators, Jira 9.5 compatibility, minor improvements This release introduces Shared conditions and Shared validators, bringing the power of Shared actions to all our workflow extensions.
Other improvements:
- Jira 9.5 compatibility
- REST APIs for shared extensions
- Support using values from before the running transition in "Copy issue fields" post-function
- Added "reverse" option for User condition and User validator
- Bugfixes
- "Transition issue" post-function now uses the specified runAsUser parameter when checking conditions for the specified transition
- Email logs for mails created using "Email issue" post-function now display the full details
For the full list of changes, please refer to the full release notes
8.0.0Jira Server 7.3.0 - 9.4.62022-10-24Major new feature: execution logs, minor improvements This release introduces a new feature "Executions Logs (Errors, Warnings, Successes)" that will help Jira Administration fix any misconfigurations in Workflow Extensions.
Other improvements:
- Event-based actions have been updated to support "Watcher added" and "Watcher removed" events and to monitor JSM fields
- Bugfixes
- Improved infinite loop detection for "Transition issue" post-function
- Support email addresses in "Run as user"
For the full list of changes, please refer to the full release notes
8.0.0Jira Data Center 7.3.0 - 9.4.62022-10-24Major new feature: execution logs, minor improvements This release introduces a new feature "Executions Logs (Errors, Warnings, Successes)" that will help Jira Administration fix any misconfigurations in Workflow Extensions.
Other improvements:
- Event-based actions have been updated to support "Watcher added" and "Watcher removed" events and to monitor JSM fields
- Bugfixes
- Improved infinite loop detection for "Transition issue" post-function
- Support email addresses in "Run as user"
For the full list of changes, please refer to the full release notes
7.3.3Jira Server 7.3.0 - 9.3.32022-08-30Bug fix release This version fixes the following bug:
- JMWE-1440 Addressed Groovy Script execution issue
7.3.3Jira Data Center 7.3.0 - 9.3.32022-08-30Bug fix release This version fixes the following bug:
- JMWE-1440 Addressed Groovy Script execution issue
7.3.2Jira Server 7.3.0 - 9.2.12022-08-25Bugfixes Highlights of this version:
- JMWE-1431: Fixed position of validation messages for "Error message" field in Scripted (Groovy) Validator
- JMWE-1422: Fixed exceptions during cache replication for messages in Jira DC
- JMWE-1383: Prevent users from creating multiple Shared Actions with the same name
- JMWE-1373: Prevent the search bar inside the script editor from overlapping with the content
For the full list of bug fixes, please refer to the full release notes
7.3.2Jira Data Center 7.3.0 - 9.2.12022-08-25Bugfixes Highlights of this version:
- JMWE-1431: Fixed position of validation messages for "Error message" field in Scripted (Groovy) Validator
- JMWE-1422: Fixed exceptions during cache replication for messages in Jira DC
- JMWE-1383: Prevent users from creating multiple Shared Actions with the same name
- JMWE-1373: Prevent the search bar inside the script editor from overlapping with the content
For the full list of bug fixes, please refer to the full release notes
7.3.1Jira Server 7.3.0 - 9.1.12022-07-20Bugfixes and improved Jira 9 compatibility Highlights of this version:
- JMWE-1430: Post functions in Shared/Scheduled/Event-based actions can now be edited in Jira 9
- JMWE-1423: Jira Service Management fields can now be accessed using JMWE on Jira 9
- JMWE-1416: Improved error message when testing Groovy scripts which incorrectly try to get the parent issue of issues without a parent
- JMWE-1394: Updated the list of available fields for Event-based actions and Field has been modified validator
For the full list of bug fixes, please refer to the full release notes
7.3.1Jira Data Center 7.3.0 - 9.1.12022-07-20Bugfixes and improved Jira 9 compatibility Highlights of this version:
- JMWE-1430: Post functions in Shared/Scheduled/Event-based actions can now be edited in Jira 9
- JMWE-1423: Jira Service Management fields can now be accessed using JMWE on Jira 9
- JMWE-1416: Improved error message when testing Groovy scripts which incorrectly try to get the parent issue of issues without a parent
- JMWE-1394: Updated the list of available fields for Event-based actions and Field has been modified validator
For the full list of bug fixes, please refer to the full release notes
7.3.0Jira Server 7.3.0 - 9.0.02022-06-16New feature, improvements and bug fixes Highlights of this version:
- You can now create new Shared, Event-based and Scheduled actions by making a copy of an existing action. The Edit and Delete buttons next to each action have been moved to a new menu that now shows Edit, Copy, and Delete as options.
- For this release, we are thrilled to introduce the new logo for JMWE for Jira Server and Data Center.
- In the Activity section of an issue, the last entry in the Transitions tab now displays the current status and time spent in that status.
For the full list of bug fixes, please refer to the full release notes
7.3.0Jira Data Center 7.3.0 - 9.0.02022-06-16New feature, improvements and bug fixes Highlights of this version:
- You can now create new Shared, Event-based and Scheduled actions by making a copy of an existing action. The Edit and Delete buttons next to each action have been moved to a new menu that now shows Edit, Copy, and Delete as options.
- For this release, we are thrilled to introduce the new logo for JMWE for Jira Server and Data Center.
- In the Activity section of an issue, the last entry in the Transitions tab now displays the current status and time spent in that status.
For the full list of bug fixes, please refer to the full release notes
7.2.0Jira Server 7.3.0 - 8.22.62022-06-01Beta support for Jira Cloud Migration Assistant and improvements This version introduces initial support for migrating to Cloud using the Jira Cloud Migration Assistant. Note that this support is currently in Beta.
Improvements
- Create/Clone issue post-function now has 'Create missing value(s)' option
- Event-based actions now support Comment Edited, Comment Deleted, Issue Deleted, and Issue Moved events
- The "Error Handling" section of the JMWE Configuration page has been rewritten for better clarity regarding options
- Copy field value (from parent, to parent, from related, to related, from field to field) post-functions have been marked as "Obsolete". We recommend that you use the more powerful and generic Copy issue fields post-function. Note that these "Obsolete" post-functions are still supported if they currently exist in workflows and actions
For more information and to see the list of bug fixes, please refer to the Release notes.
7.2.0Jira Data Center 7.3.0 - 8.22.62022-06-01Beta support for Jira Cloud Migration Assistant and improvements This version introduces initial support for migrating to Cloud using the Jira Cloud Migration Assistant. Note that this support is currently in Beta.
Improvements
- Create/Clone issue post-function now has 'Create missing value(s)' option
- Event-based actions now support Comment Edited, Comment Deleted, Issue Deleted, and Issue Moved events
- The "Error Handling" section of the JMWE Configuration page has been rewritten for better clarity regarding options
- Copy field value (from parent, to parent, from related, to related, from field to field) post-functions have been marked as "Obsolete". We recommend that you use the more powerful and generic Copy issue fields post-function. Note that these "Obsolete" post-functions are still supported if they currently exist in workflows and actions
For more information and to see the list of bug fixes, please refer to the Release notes.
7.1.4Jira Server 7.3.0 - 8.22.62022-04-18Security improvements and bug fix release This version includes a security improvement (CVE-2022-0540)
This is a recommended update for all customers.
For the list of bug fixes, please refer to the release notes
7.1.4Jira Data Center 7.3.0 - 8.22.62022-04-18Security improvements and bug fix release This version includes a security improvement (CVE-2022-0540)
This is a recommended update for all customers.
For the list of bug fixes, please refer to the release notes
7.1.3Jira Server 7.3.0 - 8.22.62022-04-03Minor improvement and bug fixes Improvement
- 'Fields to monitor' drop-down field on 'Event-based action' editor page now supports all editable fields.
For the list of bug fixes, please refer to the release notes
7.1.3Jira Data Center 7.3.0 - 8.22.62022-04-03Minor improvement and bug fixes Improvement
- 'Fields to monitor' drop-down field on 'Event-based action' editor page now supports all editable fields.
For the list of bug fixes, please refer to the release notes
7.1.2Jira Server 7.3.0 - 8.22.62022-02-22Bug fix release This version fixes the following bugs:
- JMWE-1263 Fixed Scheduled Actions issue that was updating every issue even if all post-functions are skipped by their Conditional Execution
- JMWE-1281 Fixed Run as user >> User in field options which was missing in the copy issue field post function
- JMWE-1286 Addressed high CPU load when using JMWE (groovy template inside post-function)
- JMWE-1282 Fixed the "Transition" typo on the description below the user picker field (Run as)
7.1.2Jira Data Center 7.3.0 - 8.22.62022-02-22Bug fix release This version fixes the following bugs:
- JMWE-1263 Fixed Scheduled Actions issue that was updating every issue even if all post-functions are skipped by their Conditional Execution
- JMWE-1281 Fixed Run as user >> User in field options which was missing in the copy issue field post function
- JMWE-1286 Addressed high CPU load when using JMWE (groovy template inside post-function)
- JMWE-1282 Fixed the "Transition" typo on the description below the user picker field (Run as)
7.1.1Jira Server 7.3.0 - 8.22.62022-02-10Minor bug fix This version fixes the following bug:
- JMWE-1243 Scheduled actions UI will now list its actions if there is an action with a null name.
7.1.1Jira Data Center 7.3.0 - 8.22.62022-02-10Minor bug fix This version fixes the following bug:
- JMWE-1243 Scheduled actions UI will now list its actions if there is an action with a null name.
7.1.0Jira Server 7.3.0 - 8.21.12022-02-02New feature, improvement and bug fixes Highlights of this version:
- Want to copy one or more fields either within the same issue or between issues? You can now use our Copy issue fields post-function that allows you to copy the values of one or more fields from the current issue or related issue(s) or a set of filtered issues to the specified destination issue(s).
- You can now set the value of the Tempo Account field by key or name
For the full list of bug fixes, please refer to the full release notes
7.1.0Jira Data Center 7.3.0 - 8.21.12022-02-02New feature, improvement and bug fixes Highlights of this version:
- Want to copy one or more fields either within the same issue or between issues? You can now use our Copy issue fields post-function that allows you to copy the values of one or more fields from the current issue or related issue(s) or a set of filtered issues to the specified destination issue(s).
- You can now set the value of the Tempo Account field by key or name
For the full list of bug fixes, please refer to the full release notes
7.0.4Jira Server 7.3.0 - 8.21.12021-12-22Minor improvement and bug fixes Improvement
- In the field pickers, we are now adding the field ID next to the field name. This is a useful improvement, especially when more than one field with the same name exists.
For the list of bug fixes, please refer to the release notes
7.0.4Jira Data Center 7.3.0 - 8.21.12021-12-22Minor improvement and bug fixes Improvement
- In the field pickers, we are now adding the field ID next to the field name. This is a useful improvement, especially when more than one field with the same name exists.
For the list of bug fixes, please refer to the release notes
7.0.3Jira Server 7.3.0 - 8.21.12021-12-01Minor bug fix This version fixes the following bug:
- JMWE-1191 Email Issue Post-function: Email is not sent in a few scenarios.
7.0.3Jira Data Center 7.3.0 - 8.21.12021-12-01Minor bug fix This version fixes the following bug:
- JMWE-1191 Email Issue Post-function: Email is not sent in a few scenarios.
7.0.2Jira Server 7.3.0 - 8.20.222021-11-22Minor improvements and bug fixes Improvements
- Post-functions that copy values from a text field (or a text User Property) to a user picker field now recognize email addresses and even display names, not just usernames
- The Display message to user (JMWE app) post-function now supports multiple action links
For the list of bug fixes, please refer to the release notes
7.0.2Jira Data Center 7.3.0 - 8.20.222021-11-22Minor improvements and bug fixes Improvements
- Post-functions that copy values from a text field (or a text User Property) to a user picker field now recognize email addresses and even display names, not just usernames
- The Display message to user (JMWE app) post-function now supports multiple action links
For the list of bug fixes, please refer to the release notes
7.0.1Jira Server 7.3.0 - 8.20.222021-11-10Minor improvements and bug fixes Improvements
- Joda DateTime values are now supported as Date/Time values in addition to Java Date
- The "Run As" feature now supports running as the user in a field, or a a user returned by a Groovy script
- Infinite loops are now detected for Create/Clone, Transition Related Issue and Transition Issue post-functions
For the list of bug fixes, please refer to the release notes
7.0.1Jira Data Center 7.3.0 - 8.20.222021-11-10Minor improvements and bug fixes Improvements
- Joda DateTime values are now supported as Date/Time values in addition to Java Date
- The "Run As" feature now supports running as the user in a field, or a a user returned by a Groovy script
- Infinite loops are now detected for Create/Clone, Transition Related Issue and Transition Issue post-functions
For the list of bug fixes, please refer to the release notes
7.0.0.1Jira Server 7.3.0 - 8.20.222021-10-19Minor bug fix This version fixes the following bug:
- JMWE-1163 Fixed Transition Parent Issue post-function
7.0.0.1Jira Data Center 7.3.0 - 8.20.222021-10-19Minor bug fix This version fixes the following bug:
- JMWE-1163 Fixed Transition Parent Issue post-function
7.0.0Jira Server 7.3.0 - 8.20.222021-10-12Major new features: Automation beyond Jira workflows This release introduces the following powerful, new features that allow you to run post-functions beyond Jira workflows:
- Scheduled actions
- Want to run post-functions at regular intervals? Take advantage of the Scheduled actions feature to run one or more post-functions at a scheduled interval on a specified set of issues returned by a JQL search.
- Event-based actions
- Looking for a way to run post-functions based on a specific change made to an issue, outside of a transition? Make use of the Event-based actions feature to do so whenever an event is fired.
You can also create shared post-functions and reuse them across workflows. Use the Shared actions feature to configure post-functions that can be added to several workflows transitions. This saves time and reduces your maintenance burden.
JMWE 7.0.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
- Scheduled actions
7.0.0Jira Data Center 7.3.0 - 8.20.222021-10-12Major new features: Automation beyond Jira workflows This release introduces the following powerful, new features that allow you to run post-functions beyond Jira workflows:
- Scheduled actions
- Want to run post-functions at regular intervals? Take advantage of the Scheduled actions feature to run one or more post-functions at a scheduled interval on a specified set of issues returned by a JQL search.
- Event-based actions
- Looking for a way to run post-functions based on a specific change made to an issue, outside of a transition? Make use of the Event-based actions feature to do so whenever an event is fired.
You can also create shared post-functions and reuse them across workflows. Use the Shared actions feature to configure post-functions that can be added to several workflows transitions. This saves time and reduces your maintenance burden.
JMWE 7.0.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
- Scheduled actions
6.6.1Jira Server 7.3.0 - 8.19.12021-06-04Minor bug fix This version fixes the following bug:
- JMWE-1000 ClassCastException when using XmlSlurper in Groovy script
6.6.1Jira Data Center 7.3.0 - 8.19.12021-06-04Minor bug fix This version fixes the following bug:
- JMWE-1000 ClassCastException when using XmlSlurper in Groovy script
6.6.0Jira Server 7.3.0 - 8.17.02021-06-03Minor improvements and bug fixes New features
- You can now copy from and to Insight custom fields, as well as set the value of Insight custom fields
- New getOrganization global function that returns a Jira Service Management Organization by name
- New getUsersInOrganization global function that returns the users that belong to a Jira Service Management Organization
- New organizations property on any ApplicationUser object that returns the list of Jira Service Management Organizations the user belongs to
Improvement
- When setting the "Assignee" field, you can pass "Unassigned" as the value to clear the Assignee field
For the list of bug fixes, please refer to the release notes
6.6.0Jira Data Center 7.3.0 - 8.17.02021-06-03Minor improvements and bug fixes New features
- You can now copy from and to Insight custom fields, as well as set the value of Insight custom fields
- New getOrganization global function that returns a Jira Service Management Organization by name
- New getUsersInOrganization global function that returns the users that belong to a Jira Service Management Organization
- New organizations property on any ApplicationUser object that returns the list of Jira Service Management Organizations the user belongs to
Improvement
- When setting the "Assignee" field, you can pass "Unassigned" as the value to clear the Assignee field
For the list of bug fixes, please refer to the release notes
6.5.0Jira Server 7.3.0 - 8.17.02021-04-30New features, improvements and bug fixes Highlights of this version:
- A new User Condition makes a transition available if the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc. Likewise, a new User Validator can validate that the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc.
- The Create/Clone Issue post-function can now automatically copy all fields and/or sub-tasks of the current issue to the new issue(s)
- The Email Issue post-function now allows overriding the From and Reply-to names and email addresses
For the full list of improvements and bug fixes, please refer to the full release notes.
6.5.0Jira Data Center 7.3.0 - 8.17.02021-04-30New features, improvements and bug fixes Highlights of this version:
- A new User Condition makes a transition available if the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc. Likewise, a new User Validator can validate that the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, project roles, fields, etc.
- The Create/Clone Issue post-function can now automatically copy all fields and/or sub-tasks of the current issue to the new issue(s)
- The Email Issue post-function now allows overriding the From and Reply-to names and email addresses
For the full list of improvements and bug fixes, please refer to the full release notes.
6.4.0Jira Server 7.3.0 - 8.16.12020-12-08Improvements and bug fixes Improvements
- The Jira Service Management request "channel" is now available from the Issue interface as the channel property
- The Organizations field of Jira Service Management requests can now be set by organization name in addition to organization ID
- Emails sent by the Email Issue(s) Post-Function now include an "In-Reply-To" header
- The Set Field Value Post-function now support the "run as" option
- The Comment [Related] Issues post-functions now always add the sd.public.comment comment property, even for public comments
- The Email Issue post-function now ignore recipients without an email address instead of raising an error
- The Transition related issues post-function now includes an option to trigger the WorkflowManualTransitionExecutionEvent event
- Groovy scripting: a new DateOnly class extends the Date class and allows creating date-only values, which can be created in a user's time zone. This is useful to set fields like the Due Date field.
For a list of bug fixes, see here.
6.4.0Jira Data Center 7.3.0 - 8.16.12020-12-08Improvements and bug fixes Improvements
- The Jira Service Management request "channel" is now available from the Issue interface as the channel property
- The Organizations field of Jira Service Management requests can now be set by organization name in addition to organization ID
- Emails sent by the Email Issue(s) Post-Function now include an "In-Reply-To" header
- The Set Field Value Post-function now support the "run as" option
- The Comment [Related] Issues post-functions now always add the sd.public.comment comment property, even for public comments
- The Email Issue post-function now ignore recipients without an email address instead of raising an error
- The Transition related issues post-function now includes an option to trigger the WorkflowManualTransitionExecutionEvent event
- Groovy scripting: a new DateOnly class extends the Date class and allows creating date-only values, which can be created in a user's time zone. This is useful to set fields like the Due Date field.
For a list of bug fixes, see here.
6.3.5Jira Server 7.0.11 - 8.14.12020-07-24Minor improvement and bug fix This version brings one improvement and one bug fix:
Improvement:
- When copying a String (e.g. text field) to multi-valued field types whose values cannot contain a comma, the comma is considered as a value separator
Bug fix:
- [JMWE-878] - Setting a cascading field fails in JMWE 6.3.4
6.3.5Jira Data Center 7.0.11 - 8.14.12020-07-24Minor improvement and bug fix This version brings one improvement and one bug fix:
Improvement:
- When copying a String (e.g. text field) to multi-valued field types whose values cannot contain a comma, the comma is considered as a value separator
Bug fix:
- [JMWE-878] - Setting a cascading field fails in JMWE 6.3.4
6.3.4Jira Server 7.0.11 - 8.11.12020-07-18Multiple improvements and bug fixes This version brings multiple improvements and bug fixes.
Improvements:
- Support for the Secure Fields app: when JMWE reads Secure Fields, it now bypasses security to access the value of the field
- Set Field Value post-function: better post function positioning warnings
- JMWE Validators now always display the error message on Jira Service Desk projects, including when creating a request from the customer portal
For a list of bug fixes, see the full release notes.
6.3.4Jira Data Center 7.0.11 - 8.11.12020-07-18Multiple improvements and bug fixes This version brings multiple improvements and bug fixes.
Improvements:
- Support for the Secure Fields app: when JMWE reads Secure Fields, it now bypasses security to access the value of the field
- Set Field Value post-function: better post function positioning warnings
- JMWE Validators now always display the error message on Jira Service Desk projects, including when creating a request from the customer portal
For a list of bug fixes, see the full release notes.
6.3.3Jira Server 7.0.11 - 8.11.12020-06-03Bug fix release This version fixes the following bugs:
6.3.3Jira Data Center 7.0.11 - 8.11.12020-06-03Bug fix release This version fixes the following bugs:
6.3.2Jira Server 7.0.11 - 8.9.12020-05-25Bug fix release This version fixes the following bug:
- [JMWE-858] - JMWE 6.3.0 breaks existing Related Issues Status Conditions/Validators
6.3.2Jira Data Center 7.0.11 - 8.9.12020-05-25Bug fix release This version fixes the following bug:
- [JMWE-858] - JMWE 6.3.0 breaks existing Related Issues Status Conditions/Validators
6.3.1Jira Server 7.0.11 - 8.9.12020-05-24Major bug fix This version fixes the following bug:
- [JMWE-857] - JMWE 6.3.0 breaks the Jira issue navigator when Jira Software is not installed
6.3.1Jira Data Center 7.0.11 - 8.9.12020-05-24Major bug fix This version fixes the following bug:
- [JMWE-857] - JMWE 6.3.0 breaks the Jira issue navigator when Jira Software is not installed
6.3.0Jira Server 7.0.11 - 8.9.12020-05-22New features, improvements, and bug fixes We are excited to introduce a new version of JMWE for Jira Server and Data Center. It includes several significant new features, as well as many improvements:
- Three new features in the Email Issue post-function: email attachments, display images, and explicitly exclude recipients;
- Two brand-new post-functions: display messages to users, and return to previous status;
- Flexible configurations for the Transition Activity Tab: control who can see it and on which issues/projects;
- Several new Admin tools, and conditions and validators configuration features;
- And more..
6.3.0Jira Data Center 7.0.11 - 8.9.12020-05-22New features, improvements, and bug fixes We are excited to introduce a new version of JMWE for Jira Server and Data Center. It includes several significant new features, as well as many improvements:
- Three new features in the Email Issue post-function: email attachments, display images, and explicitly exclude recipients;
- Two brand-new post-functions: display messages to users, and return to previous status;
- Flexible configurations for the Transition Activity Tab: control who can see it and on which issues/projects;
- Several new Admin tools, and conditions and validators configuration features;
- And more..
6.2.4Jira Data Center 7.0.11 - 8.9.12020-01-14Bug fix release This version fixes the following bug:
- [JMWE-832] - Transitions tab: Exception thrown while trying to call getActions()
6.2.4Jira Server 7.0.11 - 8.9.12020-01-14Bug fix release This version fixes the following bug:
- [JMWE-832] - Transitions tab: Exception thrown while trying to call getActions()
6.2.3Jira Data Center 7.0.11 - 8.6.12019-12-27Bug fix release This version fixes the following bug:
- [JMWE-825] - NullPointerException in JWME transition history panel after deleting a workflow
6.2.3Jira Server 7.0.11 - 8.6.12019-12-27Bug fix release This version fixes the following bug:
- [JMWE-825] - NullPointerException in JWME transition history panel after deleting a workflow
6.2.2Jira Data Center 7.0.11 - 8.6.12019-12-19Bugfix release This version fixes the following bugs:
6.2.2Jira Server 7.0.11 - 8.6.12019-12-19Bugfix release This version fixes the following bugs:
6.2.1Jira Data Center 7.0.11 - 8.6.12019-12-15Bugfix release This version fixes the following bugs:
6.2.1Jira Server 7.0.11 - 8.6.12019-12-15Bugfix release This version fixes the following bugs:
6.2.0Jira Server 7.0.11 - 8.5.142019-12-03Major new features This version brings the following major new features:
- A new Transitions tab under the Activity section of the issue view screen shows all transitions including, whenever possible, the name of the transition that was triggered.
- Shared Groovy scripts 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.
- All the JMWE workflow extensions that worked on linked issues 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.
- JMWE now supports the Configuration Manager app from Botron Software, which simplifies copying workflows between Jira instances.
This version also brings other significant improvements and bug fixes. For a complete list, see the full release notes.
6.2.0Jira Data Center 7.0.11 - 8.5.142019-12-03Major new features This version brings the following major new features:
- A new Transitions tab under the Activity section of the issue view screen shows all transitions including, whenever possible, the name of the transition that was triggered.
- Shared Groovy scripts 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.
- All the JMWE workflow extensions that worked on linked issues 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.
- JMWE now supports the Configuration Manager app from Botron Software, which simplifies copying workflows between Jira instances.
This version also brings other significant improvements and bug fixes. For a complete list, see the full release notes.
6.1.3Jira Data Center 7.0.11 - 8.5.142019-09-10Bug fix release This version fixes one bug:
- [JMWE-753] - Cannot load FastStringService exception when using JsonSlurper
6.1.3Jira Server 7.0.11 - 8.5.142019-09-10Bug fix release This version fixes one bug:
- [JMWE-753] - Cannot load FastStringService exception when using JsonSlurper
6.1.2Jira Data Center 7.0.11 - 8.3.99999992019-09-03Rolling back version 6.1.1 This version rolls back changes made in version 6.1.1 which would require a Jira restart to work.
At this point, the Groovy JSON parser remains broken if you have installed another app that uses an older version of Groovy.
6.1.2Jira Server 7.0.11 - 8.3.99999992019-09-03Rolling back version 6.1.1 This version rolls back changes made in version 6.1.1 which would require a Jira restart to work.
At this point, the Groovy JSON parser remains broken if you have installed another app that uses an older version of Groovy.
6.1.1Jira Data Center 7.0.11 - 8.3.99999992019-09-02Reverting to Groovy 2.4 This version reverts to the Groovy 2.4 platform to fix a conflict with other apps around the Groovy JSON parser (see JMWE-768).
6.1.1Jira Server 7.0.11 - 8.3.99999992019-09-02Reverting to Groovy 2.4 This version reverts to the Groovy 2.4 platform to fix a conflict with other apps around the Groovy JSON parser (see JMWE-768).
6.1.0.1Jira Data Center 7.0.11 - 8.3.52019-08-16New features, enhancements and bug fixes [This version is a re-release of JMWE 6.1.0 that fixes a bug in the Linked Issue Status Validator]
JMWE 6.1.0 introduces the following new features:
- The Status field can now be set directly in most post-functions
- The Issue Type field can now be changed, and the workflow of the issue will be adjusted accordingly
- In post-functions that operate on linked issues, you can now specify "any" as the link type
- When copying a field to or from the linked issues or the parent issue, you can now specify a different field to copy to
- You can now copy issue links between issues
- New getRoleMembers method on Project objects
- New isInGroup method on ApplicationUser objects
- The Multi-Level Cascading Select app is now supported
JMWE 6.1.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
6.1.0.1Jira Server 7.0.11 - 8.3.52019-08-16New features, enhancements and bug fixes [This version is a re-release of JMWE 6.1.0 that fixes a bug in the Linked Issue Status Validator]
JMWE 6.1.0 introduces the following new features:
- The Status field can now be set directly in most post-functions
- The Issue Type field can now be changed, and the workflow of the issue will be adjusted accordingly
- In post-functions that operate on linked issues, you can now specify "any" as the link type
- When copying a field to or from the linked issues or the parent issue, you can now specify a different field to copy to
- You can now copy issue links between issues
- New getRoleMembers method on Project objects
- New isInGroup method on ApplicationUser objects
- The Multi-Level Cascading Select app is now supported
JMWE 6.1.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
6.1.0Jira Data Center 7.0.11 - 8.3.52019-08-14New features, enhancements and bug fixes JMWE 6.1.0 introduces the following new features:
- The Status field can now be set directly in most post-functions
- The Issue Type field can now be changed, and the workflow of the issue will be adjusted accordingly
- In post-functions that operate on linked issues, you can now specify "any" as the link type
- When copying a field to or from the linked issues or the parent issue, you can now specify a different field to copy to
- You can now copy issue links between issues
- New getRoleMembers method on Project objects
- New isInGroup method on ApplicationUser objects
- The Multi-Level Cascading Select app is now supported
JMWE 6.1.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
6.1.0Jira Server 7.0.11 - 8.3.52019-08-14New features, enhancements and bug fixes JMWE 6.1.0 introduces the following new features:
- The Status field can now be set directly in most post-functions
- The Issue Type field can now be changed, and the workflow of the issue will be adjusted accordingly
- In post-functions that operate on linked issues, you can now specify "any" as the link type
- When copying a field to or from the linked issues or the parent issue, you can now specify a different field to copy to
- You can now copy issue links between issues
- New getRoleMembers method on Project objects
- New isInGroup method on ApplicationUser objects
- The Multi-Level Cascading Select app is now supported
JMWE 6.1.0 also adds a number of improvements and bug fixes. For more information, please refer to the full release notes.
6.0.1Jira Data Center 7.0.11 - 8.3.52019-03-11Small feature and bug fixes New feature
- New asUser() Groovy function to run some Groovy code as another user
Bug fixes
6.0.1Jira Server 7.0.11 - 8.3.52019-03-11Small new feature and bug fixes New feature
- New asUser() Groovy function to run some Groovy code as another user
Bug fixes
6.0.0Jira Data Center 7.0.11 - 8.0.32019-02-18Jira 8 compatibility and other improvements JIRA 8 SUPPORT
JMWE 6.0.0 is now compatible with Jira Software/Core 8, as well as with Jira Service Desk 4.0.
IMPROVED VALIDATORS
JMWE Validators now support a new Conditional Validation option that allows you to specify under which circumstances validation should occur. For example, if you want to make a field mandatory only if the issue is of Blocking priority, you can use the Field Required Validator together with the following condition: issue.getAsString("priority") == "Blocker"
GROOVY IMPROVEMENTS
- An isInternal() method on Comment objects to check whether a comment on a Jira Service Desk issue is Internal or Shared with customer
- A secondsBetween global function to easily calculate the duration, in seconds, between two dates
- A workdaysBetween global function to calculate the number of workdays (excluding weekends) between two dates
- The Groovy script tester page has been renamed to Groovy Console
See the full release notes for a list of bugs also fixed in this release.
6.0.0Jira Server 7.0.11 - 8.0.32019-02-18Jira 8 compatibility and other improvements JIRA 8 SUPPORT
JMWE 6.0.0 is now compatible with Jira Software/Core 8, as well as with Jira Service Desk 4.0.
IMPROVED VALIDATORS
JMWE Validators now support a new Conditional Validation option that allows you to specify under which circumstances validation should occur. For example, if you want to make a field mandatory only if the issue is of Blocking priority, you can use the Field Required Validator together with the following condition: issue.getAsString("priority") == "Blocker"
GROOVY IMPROVEMENTS
- An isInternal() method on Comment objects to check whether a comment on a Jira Service Desk issue is Internal or Shared with customer
- A secondsBetween global function to easily calculate the duration, in seconds, between two dates
- A workdaysBetween global function to calculate the number of workdays (excluding weekends) between two dates
- The Groovy script tester page has been renamed to Groovy Console
See the full release notes for a list of bugs also fixed in this release.
5.7.2Jira Data Center 7.0.0 - 7.13.182019-01-30Minor enhancements and bug fixes This version provides enhancements and bug fixes:
Enhancements:
- The Attachment field can now be set
- Jira Portfolio's new Parent-Child Link type is now supported
Bug fixes
5.7.2Jira Server 7.0.0 - 7.13.182019-01-30Minor enhancements and bug fixes This version provides enhancements and bug fixes:
Enhancements:
- The Attachment field can now be set
- Jira Portfolio's new Parent-Child Link type is now supported
Bug fixes
5.7.1Jira Data Center 7.0.0 - 7.13.182018-12-04This version provides a number of enhancements and bug fixes New feature
- A new linkIssue() method on the Issue interface allows you to easily link issues from a Groovy script
Enhancements
- The Transition Parent Issue post-function and the Transition Linked Issues post-function now warn you when adding the "Comment" field in the configuration
- The getLinkedIssues() method of the Issue interface now includes links being created on the transition screen
Bug fixes
- [JMWE-690] - The second option of the Linked Issues Validator does not work
- [JMWE-692] - Accessing a public comment of a Jira Service Desk customer request throws an exception
- [JMWE-696] - Create issue post function cannot create multiple subtasks with a calculated parent issue
- [JMWE-697] - Cannot set Cascading Field value using just a child option ID
5.7.1Jira Server 7.0.0 - 7.13.182018-12-04This version provides a number of enhancements and bug fixes New feature
- A new linkIssue() method on the Issue interface allows you to easily link issues from a Groovy script
Enhancements
- The Transition Parent Issue post-function and the Transition Linked Issues post-function now warn you when adding the "Comment" field in the configuration
- The getLinkedIssues() method of the Issue interface now includes links being created on the transition screen
Bug fixes
- [JMWE-690] - The second option of the Linked Issues Validator does not work
- [JMWE-692] - Accessing a public comment of a Jira Service Desk customer request throws an exception
- [JMWE-696] - Create issue post function cannot create multiple subtasks with a calculated parent issue
- [JMWE-697] - Cannot set Cascading Field value using just a child option ID
5.7.0Jira Data Center 7.0.0 - 7.13.182018-09-25New features, enhancements and bug fixes We are excited to announce JMWE 5.7.0, which brings improvements such as:
- A new Linked issue(s) Condition that checks issues linked to the current issue.
- A getUserProperty method on ApplicationUser objects to access User Properties (as defined on the Edit User Properties Jira admin page)
- An option on all post-functions that copy or set field values to create missing versions, component or options
- The Linked issues status Condition and Validator new allow focusing on a specfic issue type
- The Linked Issues Validator configuration has been redesigned for better clarity
- The Email Issue post-function now exposes an html-rendered version of transientVars.comment to the html body template
- The Transition [Current/Linked/Parent] Issue post-functions now support specifying multiple transitions
and more. See the release notes for details.
5.7.0Jira Server 7.0.0 - 7.13.182018-09-25New features, enhancements and bug fixes We are excited to announce JMWE 5.7.0, which brings improvements such as:
- A new Linked issue(s) Condition that checks issues linked to the current issue.
- A getUserProperty method on ApplicationUser objects to access User Properties (as defined on the Edit User Properties Jira admin page)
- An option on all post-functions that copy or set field values to create missing versions, component or options
- The Linked issues status Condition and Validator new allow focusing on a specfic issue type
- The Linked Issues Validator configuration has been redesigned for better clarity
- The Email Issue post-function now exposes an html-rendered version of transientVars.comment to the html body template
- The Transition [Current/Linked/Parent] Issue post-functions now support specifying multiple transitions
and more. See the release notes for details.
5.6.2Jira Server 7.0.0 - 7.12.32018-08-21Bug fix release This version fixes a bug that prevented configuring a Create/Clone Issue post-function with a sub-task issue type.
5.6.1Jira Server 7.0.0 - 7.11.22018-08-17Major bug fix and enhancement 5.6.0Jira Server 7.0.0 - 7.11.22018-08-17New workflow extensions, features and bug fixes We are excited to announce JMWE 5.6.0, which brings the following improvements:
- Clear field value and Clear field value of linked issues post-functions
- Set issue, user or project Entity Property value post-function to set Jira "entity properties" on issues, projects or users
- Linked issue(s) Validator to enforce the creation of issue links during the transition, with certain characteristics, or to verify the existence of such links
- An HTTP and REST client for use in Groovy scripts
- New getUrl method on Attachment objects
- New getEntityProperty, setEntityProperty and deleteEntityProperty methods on Issue, ApplicationUser and Project objects to manipulate entity properties from Groovy scripts
- The linkedIssues method on Issue objects now includes issue links being added on the transition screen
And other enhancements and bug fixes - see the full release notes for details.
5.5.4Jira Server 7.0.0 - 7.11.22018-06-15Minor bug fixes This release fixes the following issues:
5.5.3Jira Server 7.0.0 - 7.10.22018-06-12Minor bug fixes This is a minor bug fix release that fixes the following issues:
- [JMWE-638] - New Statuses are not available in conditions and validators that depend on statuses
- [JMWE-639] - Validator error message doesn't show up on recent JSD request create screen
- [JMWE-640] - Adding the Comment field on the Create or Transition Issue post-functions breaks the post-function editor
- [JMWE-641] - Setting the Comments field to a string containing a comma creates multiple comments
We have also added a Groovy Tutorial to help you familiarize yourself with the Groovy language and its use in JMWE.
5.5.2Jira Server 7.0.0 - 7.10.22018-05-26Fixes minor incompatibility with some other add-ons Bug fix:
- [JMWE-635] - Groovy tester incompatibility with certain other Jira add-ons
5.5.1Jira Server 7.0.0 - 7.9.22018-05-19Minor enhancements and bug fixes 5.5.0Jira Server 7.0.0 - 7.9.22018-05-12Integrated scripting help, and much more In this release, we've worked primarily on making JMWE scripting much easier, through a brand new integrated online help system.
We have also improved the Email Issue post-function with email templates, automatic text to html conversion, and more.
The Create/Clone Issue post-function can now create multiple issues at once and supports running a custom Groovy script over each issue created by it, among other improvements.
Other changes:
- The Scripted (Groovy) Validator can now be associated with a field, under which the error, if any, will be displayed.
- The Scripted (Groovy) post-function now supports the "run as" option
- It is now possible to activate error reporting on individual post-functions instead of setting the global error handling option on the JMWE Configuration page.
- Customer Request Type names can now be used in place of Customer Request Type IDs.
And a few bug fixes.
See the release notes for more information.
5.2.1Jira Server 6.4 - 7.9.22018-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.42018-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.42018-02-12Bug fix, two new features 5.1.0Jira Server 6.4 - 7.7.42018-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.42017-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.152016-09-23Bug fixes. Bug fixes:
4.0.4Jira Server 6.4 - 7.2.152016-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 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:
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