Workflow Post Functions
The (AUM) Copy User Property post function copies a user’s Advanced User Manager custom property value into an issue field when a workflow transition runs.
Before you start
You need Jira administrator permission to edit workflows, and at least one property definition must already exist in Advanced User Manager. Properties are created in the app under Configure → User properties. The post function’s Which property to copy? list is populated from those definitions — if the list is empty, define a property there first.
The post function is configured in Jira’s own workflow editor, not inside the Advanced User Manager console. The app’s Configure → Automation screen describes the workflow extensions and links out to the relevant Jira settings with Open workflow settings.
Add the post function to a transition
In Jira, go to Settings → Issues → Workflows and edit the workflow you want to change.
Select the transition that should copy the property.
Open Post functions and choose Add post function.
Select (AUM) Copy User Property, then continue to the configuration screen.
This screenshot shows Jira's own workflow editor. Atlassian updates it from time to time, so it may look slightly different on your site.
Configure the post function
The configuration screen is titled Copy User Property (POST-FUNCTION) and has three fields plus a live Post-function preview that restates what the post function will do.
Whose property should be copied? — select the user whose property value is read. Choose Current User to read the property of the person performing the transition, or pick a single-user field on the issue (for example Assignee or Reporter) to read that user’s property.
Which property to copy? — select one of the property definitions from Configure → User properties.
Destination issue field — select the field that receives the value.
Save the post function, then publish the workflow. As with any Jira workflow change, the post function only takes effect once the workflow is published.
The user field list can also show multi-user picker fields. Those never resolve to a single user when the transition runs, so pick Current User or a single-user field.
Field type limits
Property values are stored as text, so the Destination issue field list only offers single-value text fields. Multi-value fields and non-text field types are not selectable.
The post function overwrites whatever is already in the destination field. If the selected user has no value stored for that property, the destination field is cleared. The update is made without sending notifications.
Check that it ran: Recent executions
Open the workflow transition and look at the post function's summary. Under Recent executions it shows the last four runs: a green tick for a successful run and a red cross for a failed one. Hover over a red cross to see the error.
Troubleshooting
The property list is empty. No property definitions exist yet. Create them in the app under Configure → User properties.
Nothing is copied on transition. Check that the workflow was published, that the chosen user field actually holds a user on the issue, and that the selected user has a value stored for that property. If the user field is empty, nothing is written but the run is still shown as successful.
A red cross in Recent executions. Hover over it to read the error, for example when Jira refuses the update to the destination field.
A property was renamed. Renaming a property in Configure → User properties is safe — values follow the property, not its name.
A property was deleted. Deleting a definition removes it from the post function’s property list. Values already stored on users remain, but they are no longer displayed or available to copy.
The value comes from an external user. It cannot: the post function reads properties of Jira users only.
Related
The same user properties are also read by the AUM workflow condition and workflow validator, and are shown as property columns and in the Set properties drawer under Manage → Jira users. See the worked Post Function Example.