Hello Community,
I have an Issue where I need to fetch the CC- and TO- Participants on a new E-Mail-Ticket.
They are supposed to get copied into a new custom Field "CCParticipants". Through that I want to have a way of only keeping the Mail-Users in Loop, while not annoying all other Participants (e.G. Managers)
The Custom Field is set up as a Multi-User-Picker field ( {{CustomField 10187}}.
So in theorie, I tried to fetch the Participants on Trigger "new Issue opened" and put them into a variable for further use (with the Smart Value {{issue.Request Participants.emailAddress}} ).
I do get back the mail-addresses comma-separated.
Then I tried to write that back with the Update Issue action into my custom field.
Jira Automation tells me, that the Issue was updated corectly, but nothing changed within the field.
Any ideas? Thanks in Advance
Hi @Hendrik Laschka
This might be a good case for the 'Log Action' function in Automation. You could track what each automation step is doing and see where it's falling over.
I don't entirely understand your use-case so bear with me, but if I'm reading correctly - you're trying to populate the email addresses (comma seperated strings) into a custom field; and this custom field is a user picker type.
I suspect that may be your issue - user picker fields are expecting to get accountIds, not strings. Perhaps you could try creating a new custom field with the type set to Short text and try populating that, and see how it goes?
Alternatively, see if {{issue.Request Participants.accountId}} works with your current CCParticipants field - maybe that would satisfy your use-case?
Thanks and Regards,
Zac
Hi Zac,
The AccountID-One worked, thank you! I didnt think of that....
Reasoning behind the Automation is, that I want to separate the people, who need to be kept up-to-date for Tickets via Mail from those, who can view the Status within the Portal and dont want to recieve Mails.
Regards
Hendrik
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.