Hello everyone,
Could someone help me with this one ?
I'm trying to update a custom multi group picker from a custon single group picker.
Currently I'm trying this one :
{ "update": {
"customfield_11646": [{ "add": { "name": "{{triggerissue.customfield_11647.name}}" }
}] } }
It works great if I hard code the group name :
[{ "add": { "name": "my-group-name" }
But I need this one to be dynamic.
I also tried to display my {{triggerissue.customfield_11647.name}} in a log work, but it reamains empty.
Thank you,
Nicolas
{{triggerissue.customfield_11647.name}}
Hi Nicolas,
I just used the actual field names and it worked fine.
{
"update": {
"Approver groups": [{
"add": { "name": "{{triggerIssue.Group Single Picker}}" }
}]
}
}
Remember also that the smart values are case sensitive so it is triggerIssue and not triggerissue. Not sure if that was the difference or not.
Hi John,
Thank you so much! It works perfectly!
Is there any chance to update the Approver group with another Group Multi ? Or is it limited to Group Single Picker ?
Thanks !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It should work - the problem is if there are multiple groups already loaded in the Group Multi - but it should hopefully copy all of them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case I'd like to use only one multi group field, let's say "GroupMulti". With below scenario :
1. When an epic is created "GroupMulti" is set with the reporter's group (only one value)
2. When this epic is linked (using parent field) to an initiative, the "GroupMulti" field at Initiative level is automatically updated with the value of the "GroupMulti" at epic level.
It means that each time a new epic is linked to this initiative, a new "GroupMulti" value is added.
3. When an epic is unlinked, its value should be removed from the "GroupMulti" field at initiative level.
As i want to update the "GroupMulti" from itself at another level, I'm not sure it is possible.
This is why I tried it with 2 group fields in my first request.
@John Funk any idea ?
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have never done that process before, but I would say give it a try and see!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try to replace the name with value
As you are now referencing the CF field name and not the value set in the field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marc - Devoteam ,
Do you talk about this "name" ?
{
"update": {
"customfield_11646": [{
"add": { "name": "{{triggerissue.customfield_11647.value}}" }
}]
}
}
If so, it doesn't work either :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the log action on {{triggerissue.customfield_11647.value}} and or {{triggerissue.customfield_11647.name}}
Can you does this for the Branch, does this give a result?
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.