Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

\uD83E\uDD14 Problem

When using a 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 Create transition and

...

  • A condition that includes values from a

...

...

...

\uD83C\uDF31 Solution

  1. 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.

  1. Configure the JMWE Set issue field(s) post-function, as shown below:

The intended post-function assigns the value "First OptionExample" to the custom field (New custom fielde.g. CUSTOM_select_list_single) depending on the value from the "User Profiles for Jira" custom field.

...

...

The Conditional execution field of the post function uses the following code:

Code Block
{{ ["valuePablo 1Vergara", "value 2", "Value 3", "Value 4Other 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) in the following format:
{{ ["Value"].includes(issue.fields

.customfield_<number>)

["<CUSTOM_field_name>"]) }}

  1. 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):

Info

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.

  1. The results observed are that the desired custom field changes its value from “Third Optionvalue correctly changes to “First OptionExample”:

...

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@bc3e0baf
sortmodified
showSpacefalse
reversetrue
typepage
labelskb-troubleshooting-article
cqllabel = "kb-troubleshooting-article" and type = "page" and space = "SUPPORT"