You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are building an automation as explained in this post here.
After managing users in a list to get them only once, we just remain with the User Id information.
Now we need to send them an email, but we didn't find any API to retrive the email of the user from the Id.
Do anyone has an advice?
Can you share your rule here? Are you using the .emailAddress function at the end of the field?
We can't use emailAddress function because after we manage the list of user we lose everything except the user Id.
I didn't want to make the question too heavy since the same automation is in the linked posto, anyway here on a copy of the current automation.
As you can see at the end printing {{distinctWatchers}} print the user id, while printing {{distinctWatchers.emailAddress}} doesn't print anything.
After each step I'm sending an email to me to verify that the variables are ok.
Since there are 3 jiras with 2 different watcher only, the variable varWatcherList is an array with 3 elements.
After the second step the 2 watcher are correctly extracted.
In the second part of the jira I want to dinstict the watcher.
For every watcher I send to me this email, but the emailAddress and displayName is empty
Here the result for the 2 watchers.
So, what I miss is to extract the email address because the last step is this:
And emailAddress is always empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.