Been at this for hours and it's starting to drive me nuts, so any help is really really appreciated.
In the "More Options" portion of one of my automations that transitions issues, I have this bit of code:
{
"update": {
"Request participants" : [
{
"add": {
"id": "[~accountid:{{issue.customfield_11200}}]"
}
}
]
}
}
It is taken directly from the Request Participants example on Jira's support page, and yet it errors out every time saying that no valid value was supplied for the update to customfield_10130, which is Request Participants. https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
This tells me that I'm targeting that Request Participants successfully, but for some reason Jira refuses to take the value I've supplied, a user from a different custom field, as an input. I believe I'm following documentation to a T, but clearly I'm doing something wrong.
Anyone do this before with any degree of success?
Hi @Ian Guyette
You could try, the following
{{issue.customfield_11220.accountId}}
{
"update": {
"Request participants" : [
{
"add": {
"id": "{{issue.customfield_11220.accountId}}"
}
}
]
}
}
Or in your automation you should create a variable that will get the account ID from the user specified in customfield_11200
Then use that variable in the more options
Thanks so much Marc, bad syntax on my part it seems. Have a great day!
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.