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?
You need to edit the assignee field with a smart value. In this case it will be the {{issue.developer.accountId}}
Some examples here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/
I hope this helps
Hi @Paisley Greer -- Welcome to the Atlassian Community!
Adding to Fabian's answer...
It may not be obvious how to enter the smart value for the fields with drop-downs. To do this:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fabian Lim @Bill Sheboy Thanks for the feedback. I tried pasting {{issue.developer.accountId}} in the highlighted box and now I get the following error. I'm not quite sure what to do in the "Additional Fields" section.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.