Note |
---|
This post-function has been deprecated and replaced by Set field valueissue fields. 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. |
Configuration details
Field - Select the field to edit.
Value type - The value to be set can be either a constant, derived from a Groovy template, or can be dynamically determined using a Groovy expression.
Constant or Groovy Template
Groovy Expression
Value - The constant value, Groovy template, or Groovy expression to use for determining the field value.
Options
Set only if empty - Sets the value of the selected field only if the field is empty.
Ignore empty values - Will not set (clear) the selected field, if the value is empty or null.
Add value(s) to destination field - Only valid for multi-valued fields. Appends the specified value(s) to the selected field of the current issue.
Remove value(s) from selected field - Only valid for multi-valued fields. Removes the specified value(s) from the selected field of the current issue.
Create missing value(s): 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.
Run as
Run as user: Select one of the following options to set the author of the action performed by this post-function as:
Current user: The user transitioning the issue.
Specific user: The user specified in the select-list provided. Start typing into the field to select a user from the list of auto-suggestions.
User in field: The user specified in a user picker field of the issue being transitioned. Select one of the user fields from the list of available options in the field provided.
User from script: The user returned by the Groovy script specified in
Script
. This script should return either the Username of the user or an ApplicationUser object. For example:"jdoe"
- Usernameissue.get("assignee")
- the current issue's Assignee
Conditional execution
To execute this post-function based on the result of a groovy expression, check this option. See Conditional execution/validation using a Groovy expression for more information.
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
.