Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Set field value

Owned by Radhika Vijji. (Unlicensed)
Last updated: Jun 16, 2022 by Richard Stone[Appfire] (Deactivated)
4 min read



Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here.

 

 

A workflow post-function that sets the value(s) of a selected field of the current issue. The value can be either a constant, optionally including a Groovy template markup, or the result of the evaluation of a Groovy expression.

To add the 'Set field value' post-function to a transition:

  1. Click Edit for the workflow that has the transition you wish to configure the post-function on.

  2. In the Workflow Designer, select the transition.

  3. Click on Post Functions in the properties panel.

  4. Click on Add post function.

  5. Select Set field value from the list of post-functions.

  6. Click on Add to add the post-function on the transition.

     

  7. Select the field from the Field drop-down.

  8. Select the value type from the Value type drop-down.

  9. Input a value in the Value field based on the value type selected in step 8.

  10. Click on Add to 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 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.

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 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.

  • 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.

    Examples:

    • "jdoe" - Username

    • issue.get("assignee") - the current issue's Assignee

Conditional execution

To execute this post-function based on the result of a groovy expression see Conditional execution/validation using a 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.