When you add this post-function to a transition and trigger it, the add-on sets the selected field of the current issue to the specified value. The value can be either a:
- Constant or Groovy Template: You can set the field to a constant value optionally using Groovy Template markup to insert dynamic content. For example: To set the Description of the issue, you can specify
This bug has been raised by <%=issue.get("reporter").getName()%> with <%=issue.get("priority").getName()%> priority. Act accordingly. in the value box.
- Groovy expression: You can set the field to the result of a Groovy expression. For example, to set the Assignee to the Reporter of the issue, you can specify
issue.get("reporter") in the value box.
See the Expected Value tab of the
Groovy help editor or refer to the documentation to know more about the expected value in the above cases.
Sets the value of the selected field only if the field is empty.
Will not set (clear) the selected field, if the value is empty or null.
- Add source value(s) to destination field
Appends the specified value(s) to the selected field of the current issue. This is applicable only to multi-valued fields.
Allows automatically creating any missing value(s) while setting a field value. This is applicable only to Affects Version/s, Fix Version/s, Single version and Multi-version picker type custom fields, Components, Radio buttons, Checkboxes, Single select and Multi-select list type custom fields.
Any user specified in this field will be the author of the field change performed by the post-function. Leave it blank for the current user to be the author. Note that this will only have an effect on the issue History if the post-function is positioned after the 'Creates the issue originally' or the 'Update change history for an issue and store the issue in the database' built-in post-function.
To execute this post-function based on the result of a groovy expression see Conditional execution/validation using a Groovy expression.
By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file but will not be reported to the user and will not prevent the transition from completing.
However, when designing new workflows or troubleshooting them, it is more convenient to be notified immediately of any such error during the execution of the transition. On development and staging Jira instances, you can activate error reporting for all JMWE post-functions on the JMWE configuration page, and it is recommended to do so. But on production Jira instances, you might want to show errors only for the post-function(s) being worked on, in order to avoid disrupting other workflows. To make errors raised by the current post-function prevent the transition from completing and show the error in the browser, select
Make transition fail when an error occurs in this post-function.