When you add this post-function to a transition and trigger it, the add-on sets the specified value(s) on the selected field of all issues linked to the current issue through a selected link type. The value can be either a:
This bug has been raised by <%=issue.get("reporter").getName()%> with <%=issue.get("priority").getName()%> priority. Act accordingly.
in the value box.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.
Beware of the default "relates to" link type, which can cause confusion. The problem stems from the fact that "relates to" is both the inward direction and the outward direction of the "Relates" link type. We recommend that you rename one of the directions to "is related to" to avoid confusion. This can be done on the Issue Linking Jira admin page. |
Sets the value of the selected field on all linked issues only if the field is empty on the linked issues.
Will not set (clear) the selected field of linked issue(s), if Value
is empty or null.
Appends the specified value(s) to the selected field of all the linked issues. This is applicable only to multi-valued fields.
Allows automatically creating any missing value(s) while setting a field value of linked issue(s). 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 copy performed by the post-function. Leave it blank for the current user to be the author.
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
.