Copying a Multi-Select Field to a Child Upon the Transition of the Parent

[Kellie Noumi]

Hi everyone,

I am hoping someone can help me with an issue that is driving me nuts.  :) This is my first time posting, so please bear with me.

i have a field called Dev Team that is a multi-group picker field.  I have set up an automation to copy the status to all children when a parent is updated.  In that automation, I have asked for the Dev Team to be copied to the child issue, and it will not populate.  I tried to use a custom script, and that also did not work.   

Any ideas?

[Trudy Claspill]

Hello @Kellie Noumi 

The first issue is that you should not edit a field both by selecting the field in Choose fields to set and manipulating the field in the JSON editing option. You should only ever use one method of the other to edit a field in a single action.

Next, I have a question. Do you want to overwrite anything that is already in the Dev Team field in the child issues with everything that is in the Dev Team field of the parent issue? Or are you trying only to add values from the Parent issue to the Child issues?

[Kellie Noumi]

Hi there,

Thank you so much for your help.   I tried them both separately, but included them both in the screenshot so that everyone can see what we have tried.

I would say to add values, although the reality is that the field will be blank until the transition happens 99.5% of the time.  So, if it needs to replace values, I think that could work.

Thanks so much for your help.  So appreciate it.

[Trudy Claspill]

What is the output in the Audit Log from executing the rule when you had the field selected only from Choose fields?

The rule will not be successful in setting the field through the Transition Issue action if you don't have a Screen associated with that transition, where the screen includes the field. In the Audit Log for the rule execution you would see an error message like:

"The fields set during transition aren't available. Fields ignored:"

If you don't or can't add a transition screen, then you will need to use a separate Edit Issue action to set the field.

In whichever action you use, make sure you delete the JSON code that is trying to set the field.

Click the ... button to the right of the field and select COPY.

Click on the text that appears.

Change the source issue to Parent Issue and check the box for Add Values.

[Kellie Noumi]

Thank you so much for your help.  I so appreciate it.

I made the updated and the Dev Team field still will not populate.  This is how I had it set up originally with no success.   Here are the screenshots.  Am I doing something wrong?

[Trudy Claspill]

In the audit log, please click on all the expansion arrows on the right to reveal the details of all the log entries and share the screen image of the log again.

Are the parent and child issues in the same project? Can you provide a screen image for the parent issue including showing the portion of it that lists the child issues? From the images you provided it looks like the parent issues may be in IDEAS and the child issues in JTP.

What is the Project Scope of the rule, specified on the Rule Details page? If the Parent and Child issues are in different projects all the relevant projects must be specified in the project scope. Multiple Project scoped rules can be configured only by Jira Product Administrators.