A workflow post-function that sets the value of a user, issue or project Entity property. The value can be either a constant or the result of the evaluation of a Groovy expression or the result of a Groovy template.
To add the 'Set issue, user or project Entity Property value' post-function to a transition:
- Click Edit for the workflow that has the transition you wish to configure the post-function on.
- In the Workflow Designer, select the transition.
- Click on
Post Functionsin the properties panel. - Click on
Addpost function. - Select
Set issue, user or project Entity Property valuefrom the list of post-functions. - Click on
Addto add the post-function on the transition..png?version=1&modificationDate=1533585862592&cacheVersion=1&api=v2&width=500&height=536)
- Select the entity from the Entity drop-down.
- Input the name of the property in the
Property namefield. - Select the value type from the
Value typedrop-down. - Input a value in the
Valuefield based on the value type selected in step 9. - Click on
Addto add the post-function to the transition.
Related links :
For information on where the post-function needs to be placed on a transition, see Placing post-functions on a transition.
Refer to the Use cases for post-functions page for use cases for this post-function.
When you add this post-function to a transition and trigger it, the add-on sets the property of the selected entity to the specified value. The value can be either a:
- Raw value, when you select
Constant or Groovy Templateas the Value type. - Result of a Groovy expression, when you select Groovy expression as the
Value type.See- Groovy editor in JMWE to write your Groovy script
- Expected Groovy expression input for each field
- issue, currentValue, currentUser and log variables you can use in your Groovy script
- Accessing the fields of an issue to use them in your Groovy script
- Groovy tester to test your written your Groovy script
- Result of a Groovy template, when you select
Constant or Groovy Templateas theValue type. See- Groovy editor in JMWE to write your Groovy templates
- Expected Groovy expression input for each field to write your Groovy templates
- issue, currentUser, textutils and log variables you can use in your Groovy templates
- Accessing the fields of an issue to use them in your Groovy templates
- Groovy tester to test your written your Groovy templates
Options
- Set only if property is empty
Sets the property value only if the property is currently empty.
- Ignore empty values
Will not set (clear) the selected property, if the value is empty or null.
Conditional execution
To execute this post-function based on the result of a groovy expression see Conditional execution using Groovy expression.
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.