Info |
---|
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here. |
Note | ||||||
---|---|---|---|---|---|---|
Documentation for
|
Note |
---|
This post-function has been deprecated and replaced by Set field value. It could be removed at any time. You can still use it, but it is highly recommended that you update any workflows that use this post-function. |
Panel |
---|
Related links : |
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 related to the current issue through a selected link type. 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 <%=issueget("reporter").getName()%> with <%=issue.get("priority").getName()%> priority. Act accordingly. 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.
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.
Input a Groovy expression that returns true if the post-function should run. For more information see Conditional execution using Groovy expression. Note that the condition will be evaluated once per applicable related issue, with each related issue being available, in turn, in the relatedIssue and deprecated linkedIssue variables.
Error Handling
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.