Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Creation of a new task sets assignee as 'Unassigned'
Ideally staff would set a user but at creation a user is not always decided on.
Problem arises when trying to exalate one of these tasks.
Prior to this situation coming up I was simply using
Error Detail Message:
Cannot get property 'displayName' on null object
Error line: 18
To try and solve I believe this should work as something very similar worked under visual mode.
Note: I am only passing the displayName as the user is not on the replica instance and is simply displayed on a custom field.
You can try to do instead:
Kind regards,
Ariel
Thanks for the suggestion, Unfortunately that just results in error:
Cannot cast object 'Unassigned' with class 'java.lang.String' to class 'com.exalate.api.domain.hubobject.v1_2.IHubUser'
If you just do:
What are you trying to achieve here?
Kind regards,
Ariel
This doesn't work as the users are not available on both sides. When we were using the visual method of connection to get around this I would set a custom text field to indicate the Reporter and Assignee.
as shown here
I didn't think this should be hard to do but am quite stuck I simply want to set a custom field as the name text ie .displayName and if its a null then set any other string ,ie "Unassigned" or "N/A".
The elvis operator '?:' was working under visual so its odd it wont work here.
Is the remote assignee correct?
Maybe it should be replaced to: