\uD83E\uDD14 Problem
When using a “Set Issue Field” on a Create transition with information from “User Profiles for Jira” on a custom field used on a condition“Set Issue Field(s)” post-function on the Create transition and using a condition that includes values from a “User Profiles for Jira” app custom field, fields are not correctly set.
...
\uD83C\uDF31 Solution
Replicate the configuration considering the custom field being utilized used and its settings .as follows:
Custom field created by User Profiles for Jira | Text Field (read-only) |
Second New custom field | Select List (single choice) |
Info |
---|
When assessing the functionality of the "User Profiles for Jira" custom field, it is observed that the fields functionality, we noticed that this third-party app takes some time to populate the value of the necessary field. |
Build the 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 (second New custom field) depending on the value of from the "User Profiles for Jira" custom field. Here is the configuration of the post-function:
...
Code Block |
---|
{{ ["value 1", "value 2", "Value 3", "Value 4"].includes(issue.fields.customfield_<number>) }} |
As the third-party app does take a while to populate the custom field, it is necessary to include a delay in as part of the post-function configuration (in the example delay in this case is 15 sec., we have set a 15-sec delay for testing purposes):
Info |
---|
IMPORTANT: Use the minimum working delay duration possible and test. 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 changes its value from “Third Option” to “First Option”“Third Option” to “First Option”:
...
\uD83D\uDCCE Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|