We have automation that looks like this:
for {items} {
for {items} {
"update": {
"customfield_X" : [
{
"add": { "value":items }
}
]
}I.e. we update the same issue in cycle - adding values to multipicker CF.
The issue is - update is just launching the update procedure, as the result some updates are running in parallel. And not all values from {items} list are in CF.
Example:
{A, B, C} in list
{A, C} - in CF as the result.
Issue history contains:
{}->{A}
{A}->{A,B}
{A}->{A,C}
so the first update was completed before the second started
but the second update wasn't completed as the third started.
Is the any known solution?
Thanks in advance,
Alex,
Community moderators have prevented the ability to post new answers.
Hello @Alex Kiselev _Itransition_ ,
Thanks for reaching out, and I am having some difficulty recreating the rule you are using with the details provided.
Can you grab a screenshot of the rule configuration page, and include the full syntax of the JSON as you have it formated for the Edit issue action, so I can get a better understanding of how you have this setup?
I am particularly interested in the "For" section as well as the full syntax for the edit action JSON. i.e. for the "For" section, are you using "Advanced Branching" and setting a smart value, and what is the smart value you set, or are you using a "Related issues" branch rule referencing the current issue?
Regards,
Earl
Hello @Earl McCutcheon
Thank you for the help.
Actually, we have found the solution:
we use API calls for update operation with the "Wait for response" option instead of Update field action in the rule.
Best regards.
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.