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.
Hello. Since our move to the Cloud, I've found that smart values for assignee and reporter both are rendering as "@user". How do I fix this? Thanks in advance!
Hi @Michael Aniskovich - could you please share a screenshot of where you are seeing @user instead of the expected smart values for assignee and reporter?
You're using Automation for Jira, and migrated your rules as well?
One significant difference between on-prem and Cloud is that user IDs are no longer usernames (like darryllee), but rather a unique/unguessable ID like 123456:55ffffff-d999-4ddd-bbbb-bf9999999c4f
This was done for GDPR compliance. There's an old announcement about it here:
And a bit more about it here, with regards to Automation:
Now that I read that, I'm wondering if perhaps you have some automations to send emails to {{reporter}} or {{reporter.name}}, and they're now saying things like:
Hi 557058:5aedf933-2312-40bc-b328-0c21314167f0, Please respond. Cheers Atlassian
Instead of:
Hi johns, Please respond. Cheers Atlassian
As that page mentions, one possible "fix" is to change that smart value to {{reporter.displayName}}.
Please let me know if this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.