Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation for Editing Issue Fields when an issue is Transitioned

Paisley Greer July 26, 2022

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:

 

Screenshot 2022-07-26 163645.png

 

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?

 

Screenshot 2022-07-26 163939.png

 

1 answer

1 vote
Fabian Lim
Community Champion
July 26, 2022

Hi @Paisley Greer

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 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 26, 2022

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:

  • type in (or paste in) the smart value expression
  • and it will appear below the field
  • when it does, select it and the expression will be used for the edit.

Kind regards,
Bill

Like Fabian Lim likes this
Paisley Greer July 27, 2022

@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.

Screenshot 2022-07-27 144256.png

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2022

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.

Paisley Greer July 27, 2022

@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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2022

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events