Why my automation rule returns success but only updates standard fields and not customized fields?

[isabel_p_cardoso_hotmail_com]

I have created a rule to add on User story, custom field Developer Assignees (that is a field that takes multiple assignees) to the same value of the sub-task assignee but that field does not update. I have tested the same rule using the standard field Assignee on the User story and that works fine. It's like the automation does not ready the custom field at all, even though is says success.

[Hans Polder _Devoteam_ · Accepted solution]

Hi Isabel,

Welcome to the community!

Your current rule is actually copying the Developer Assignees field from the Sub-task, to the parent.

But, it seems like you want to use the Assignee value from the Sub-task to fill the Developers Assignees field in the parent, correct?

If that's the case, you'll need to click on the 'Copy Developers Assignees from Trigger issue' link, which will show a popup, in which you can state that you want to use the information stored in the Assignee field to copy over to the 'Developers Assignees' field in the parent.

Have you tried that already?

[isabel_p_cardoso_hotmail_com]

You are right! That was so silly! Thank you so much for your help. I do have another problem related to the same rule. Since I selected to ADD values in the edit issue fields, now I can't actually remove previous added assignees to reflect the reality of the sub-tasks of the parent issue.

For instance, if one single sub-task changes assignees 3 times, the parent will show 3 different value and not the latest value in the sub-task. I can't use the copy option only because if a parent has multiple sub-tasks, it will only show the latest sub-task assignee updated. How can I show the assignees that are currently working at the sub-tasks without stacking values?
Thank you so much for your help so far!

[Hans Polder _Devoteam_]

Hey Isabel,

Interesting case. I think this can only be solved by using the 'lookupIssues' action, like so:

- If the assignee changes

- Condition: Issue Type = Sub-task

- Branch 'for Parent'

- Lookup issues searching for all sub-tasks in the Parent

- Use the output of the lookup Issues to identify all unique assignees in the related sub-tasks

- And fill this in the Assignee field of the Parent of the sub-task.

I don't have much experience with using the output of lookupIssues, but if you search a bit more on the community and try it out first yourself, you might be surprised to what you can accomplish. If you don't succeed, feel free to post your results/findings here so we can further test out/trouble shoot.

[isabel_p_cardoso_hotmail_com]

Maybe I am doing the iteration wrong, because I can't see any values from the formula I applied on the step create variable: {{lookupIssues.assignee.displayName}}
Can you help me with this? I am trying to learn how to do this JQL for lookIssues but I am stuck.