Automation for Editing Issue Fields when an issue is Transitioned

Question

Trying to add an automation so that, when an issue is transitioned into QA, the "Assignee" then becomes the "Developer" (a custom field). The automation is not working.

So far, I have the following automation:

The possible issue could be that because Developer is a custom field, it is more than likely trying to find the built in field of "Developer" like we have on other projects.

Do I need to fill out something in this field to get it to work?

Bill Sheboy · Answer

Smart values are case-sensitive and spacing-sensitive; when you have an incorrect one, it just returns null.

To check that, you can use this how-to article.  Basically, you are calling the REST API for an example issue with a browser, finding your field, and checking the smart value:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

You may also use the custom field ID number in place of the name.

Paisley Greer · Answer

@Bill Sheboy @Fabian Lim Thanks for that. I was able to clear out that section.

However, my automation still is not working. When I move the issue to QA, the Assignee still does not become the Developer (which is a custom field).

Bill Sheboy · Answer

I believe that is from the template stuff in the "More options" section.  Unless you need the JSON edit, clear everything in that "Additional fields" area, collapse "More options", and then publish/re-test your rule.