Set field value from User Entity Property value

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 :

Click Edit for the workflow that has the transition you wish to add the post-function on.
In the Workflow Designer, select the transition.
Click on Post Functions in the properties panel.
Click on Add post function.
Select Set field value from User Entity Property value from the list of post-functions.
Click on Add to add the post-function on the transition.
Select the field name from the Field drop-down.
Input the user property key name in the User entity property field.
Click on Add to add the post-function to the transition.
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

Post functions are provided with an option to delay execution for a set number of seconds using the Delayed execution option (Figure 1, right). To delay execution, select the number of seconds to wait until the post-function is run; any value between 1 second (the default) up to a maximum of 20 seconds can be selected.

Workflows that depend on post functions being executed in a specific order can fail due to the asynchronous nature of Connect post-functions in Jira Cloud. One workaround is to delay the execution of a post-function, thereby creating a more predictable execution order. For example, on the approval of a Story you want to create sub-tasks and immediately transition them; in this case, you will have to delay the execution of the Transition Linked Issues post-function, so that the sub-tasks are created before they are transitioned. See the sample use case, below.

Where possible, it is recommended to use the Sequence of post-functions post-function or Shared action post-function to execute a series of post-functions in a specific sequence instead of applying a delay.

Sample use cases for Delayed execution

On the creation of a Bug, assign it to a member of the QA team and then add the Assignee to the Watchers.

Steps

Create a QA project role, with the testers as its members.
Add the Assign to role member post-function to the transition Create of the Bug workflow.
Select QA as the project role to look for.

Add the Copy value from field to field post-function to the Create transition of the Bug workflow.
Select Assignee as the From field.
Select Watchers as the To field.
Select the Delayed execution option and select 5 sec from the Delay drop-down.

On the approval of a Story, create subtasks for Development and QA, and transition them to In Progress status.

Steps

Add the Create issue post-function to the Approve transition of the Story workflow.
Select Same as current issue from the Project field.
Select Subtask from the Issue type field.
Select Current issue from the Parent issue field.
Repeat the above steps for the Development subtask.

Add the Transition linked issues post-function to the Approve transition of the Story workflow.
Select Issue Link Type as is Parent of.
Select the Delayed execution option and select 10 sec from the Delay drop-down.

You are viewing the documentation for Jira Cloud.