...
When using a “Set Issue Field(s)” post-function on the Create transition and using a condition that includes values from a “"User Profiles for Jira” app (Atlassian Marketplace link: https://marketplace.atlassian.com/apps/1212508/user-profiles-for-jira) provided custom field, fields are the latter is not correctly set.
...
\uD83C\uDF31 Solution
Replicate the configuration considering the custom field being used and settings as follows:
Custom field created CUSTOM_user_profile_jira field (provided by User Profiles for Jira app) | Text Field (read-only) |
New custom fieldCUSTOM_select_list_single | Select List (single choice) |
| Info |
|---|
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 of the field. |
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 (New custom field) depending on the value from the "User Profiles for Jira" custom field.
...
| Code Block |
|---|
{{ ["Pablo Vergara", "Other User"].includes(issue.fields |
...
["CUSTOM_user_profile_jira"]) }} |
| Info |
|---|
Remember what’s shown below is an example, and you would need to use and replace your own custom field name (or id) following the |
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):
...
The results observed are that the desired custom field changes its value from “Third Option” value correctly changes to “First OptionExample”:
...
\uD83D\uDCCE Related articles
...