\uD83E\uDD14 Problem
The Set Issue Field(s) post-function does not correctly set its configured field(s) when using the following:
The “Set Issue Field(s)” post function on the
Createtransition andA condition that includes values from a custom field provided by "User Profiles for Jira” (Atlassian Marketplace link: https://marketplace.atlassian.com/apps/1212508/user-profiles-for-jira).
\uD83C\uDF31 Solution
Replicate the configuration considering the custom field being used and settings as follows:
CUSTOM_user_profile_jira field (provided by User Profiles for Jira app) | Text Field (read-only) |
CUSTOM_select_list_single | Select List (single choice) |
When assessing the "User Profiles for Jira" custom fields functionality, we noticed that this third-party app takes some time to populate the field's value.
Configure the JMWE Set issue field(s) post-function, as shown below:
The intended post-function assigns the value "First Option" to the custom field (e.g. New custom field) depending on the value from the User Profiles for Jira custom field.
The Conditional execution field of the post function uses the following code:
{{ ["Pablo Vergara", "Other User"].includes(issue.fields["CUSTOM_user_profile_jira"]) }}
Remember what’s shown below is an example, and you would need to use and replace your own custom field name (or id) in the following format: {{ ["Value"].includes(issue.fields["<CUSTOM_field_name>"]) }}
As the third-party app does take a while to populate the custom field, it is necessary to include a delay as part of the post-function configuration (in the example, we have set a 15-sec delay for testing purposes):
IMPORTANT:
Use the minimum working delay duration possible and test thoroughly. If the result is unexpected, increase it by one second and test again until the post-function properly sets the field value.
The results observed are that the desired custom field value correctly changes to “Example”:
