Hello everyone,
I created a new User custom field of field type "User Picker" which was created out of the necessity to have multiple assignees per issue.
Now I want to introduce an automation rule that sends a mail to the new assignee in the event that one is added.
How do I manage to only address the newly added member, without sending a mail to all previous assignees as well? I am struggling to use the smart value {{fieldChange}} for this, as it only fetches strings at best and I cannot get the email address from this.
Any advice is highly appreciated, thanks in advance
Best Regards
Daniel Triftshaeuser
Hey everyone!
The trick is not using the {{fieldChange}} variable as you might initially think. I have posted a complete elaboration on this question. I hope it helps!
Best
Simon
Hey Simon,
thanks for your detailed write-up on the other question.
The topic has lost some of its urgency since I first asked the question here, who would have guessed :D
I'll be sure to test your solution when I get around to it and let you know if that works / would have worked for my use case.
BR
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries, I figured. :P
I just put it here for completeness in case anyone else comes across this post looking for a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm trying to do the same thing 2 years late. Anyone able to do this yet?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daniel,
Thanks for reaching out.
Unfortunately, that is not possible at the moment. You were going down the right track, fieldChange is the correct thing to use, but it only gives you the accountId.
We have an open issue in the backlog to implement a way to use this to find the complete user (with email).
https://codebarrel.atlassian.net/browse/AUT-725
Sorry,
Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Scott,
thank you for you answer.
What a shame, but hey at least it is being looked into.
Best Regards
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.