Tempo Structure formulas different behaviour in cloud compared to data-center

[Chris Smith]

Im trying to test migration of some structures from Data Center to Cloud, and have come across some weird behaviour and wonder if anybody knows what I am running into and how to handle it. I have columns in many structures that use constructs like this

issuelinks.MAP($.source.MyCustomField)

or

issuelinks.MAP($.source.assignee)

All of these give blank responses.

If I do

issuelinks.MAP($.source.summary)

then I do get the summary. But all other attributes that I test come back blank (whereas they work on data-center of course).

I've looked at the documented list of differences but dont find anything that looks like this. Anybody recognize this?

[Stepan]

Hello @Chris Smith 

In Structure Cloud, the issuelinks function has very limited access to attributes right now. You can find the list in our documentation here. We have plans to expand it in the future; until then, we recommend to add the linked items to the structure, and access their field values directly. I.e. instead of extracting a custom field value of a linked item via the issuelinks function, you can add this item to the structure as a sub-item to its linked parent, and use an aggregate function to show the sub-item's value for its parent at the top, like this: max#children{customfield}

Also, I recommend to check out the full list of differences in Formula functions between Data Center and Cloud here.

I hope this helps. If you have more questions about Structure, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)