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 from User Entity Property value

Owned by Radhika Vijji. (Unlicensed)
Last updated: Sept 04, 2020
2 min read

A workflow post-function that sets the value of a selected field of the current issue to the value of a User Property of the current user.

To add 'Set field value from User Entity Property value' post-function to a transition : 

  1. Click Edit for the workflow that has the transition you wish to add 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 User Entity Property value from the list of post-functions.

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

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

  8. Input the user property key name in the User entity property field.

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

  10. After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.

Known limitations common to all post-functions:

Related articles:

JMWE shows an error message on the issue view if any error occurs during the execution of the post-function. This message is displayed only if the current user is a Jira administrator. 

When you add this post-function to a transition and trigger the transition, the add-on copies the value of the specified user property for the current user to the selected destination field. The user property is used to store extra information about a user. These properties come from the User properties editor page in the Add-ons section. These properties are different from the User Properties you can edit from the User Management section. To add/edit user properties of a user, see the Add/edit/delete user entity properties in User property editor page. 

Options

  • Create missing value(s): Allows creating any missing Component/s or Version/s while setting or copying a field that expects Versions or Components. Note this is applicable for version and component fields.

When setting the Issue Security field, the user property must contain the name of the Security Level, which you can find by looking at the links associated with the Add/Default/Delete operations on the desired Security Level (on the Edit Issue Security Levels screen).

Conditional execution

To execute this post-function based on the result of a Nunjucks template see Conditional execution.

Run As

  • Run as current user: The current user will be the author of the field change.

  • Run as add-on user: The add-on user will be the author of the field change. 

  • Run as this user: Any user selected in this field will be the author of the field change.

Running this post-function as any user other than the "Add-on user" is discouraged

If you select any option other than "Run as add-on user", so that the change appears to be done by the current user or a specific user, the following must be true:

  • The destination field must be present on the Edit screen applicable to the issue being modified

  • The selected user must have the Edit issues permission on the issue being modified

Delayed execution