Smart Value displays values in audit log but not in web post payload (blank values sent)

[Ryan Danowski]

We created a smart value that gathers selected users in a form.  We called it Group.  When using the advanced branch to iterate through the users of the group.  We give each iteration the variable name of "person" in the advance branching section. I can see the user values ({{person.displayName}}, {{person.emailAddress}}) when having the iteration log to the audit log.  But when we go to post these to a web request post, the values are blank.

Replaced names and emails with ***** for privacy.  But its does output the full name and email to the log

Example Audit Log Results -

Log

{ "displayName": "Cole H******", "emailAddress": "cole.******@******.com", "component": "Box" }, { "displayName": "Ryan D*******", "emailAddress": "ryan.**********@*********.com", "component": "Box" }

For our web request we are using a custom data field and using this as the posted data

{
"displayName": "{{person.displayName}}",
"emailAddress": "{{person.emailAddress}}",
"component": "{{issue.components.name}}"
}

It should send the above payload 1 iteration (person) at a time for each person, which it does, except that the values for displayName and emailAddress are coming back blank.

Example Web Request Post payload results -

Payload
{
"displayName": "",
"emailAddress": "",
"component": "Box"
}

I dont understand why this smart value is not working to send the payload data we need to bettercloud to run a workflow against the data.  Any ideas?

We can send {{issue.group.displayName}} or {{issue.group.emailAddress}} and that will show up with all of the users names and email addresses in the payload sent together.  But that doesnt help if we want to iterate through the list of them one at a time.  It seems like its breaking during the advance branching section.  But only on the web request post action.  And not on writing the users to the audit log.

Any help would be greatly appreciated!

Thank you!

[Bill Sheboy]

Hi @Ryan Danowski -- Welcome to the Atlassian Community!

That is an interesting behavior...it seems to indicate the advanced branch variable is using object data to decide to anonymize it, or that something else in the web request action is doing so, or...?

First thing, I would partner with your site admin to submit a support ticket to Atlassian at this link, and then post back here what they find/respond: https://support.atlassian.com/contact/#/

Next, have you considered a work-around where you first store the branch loop values in a created variable (thus converting them to plain text) and then trying to use them in the web request?  That would rule out if it is object data versus the web request action itself doing this anonymizing.

Kind regards,
Bill

[Ryan Danowski]

Thanks @Bill Sheboy .  Those are great suggestions.  Will get back with what we find!