Auto Assign an Epic based on a user picker custom field

[Elif Alverson]

Hello, 

I am trying to auto assign an epic based on a required user picker custom field called HTBP which is filled at the ticket creation. Here is my automation and not sure how to continue? Thank you.

[Trudy Claspill · Accepted solution]

Hello @Elif Alverson 

Instead of Specify User you need to change that to Another field value or comment, then you will be able to specify the custom User Picker field from which you want to copy the user.

[Elif Alverson]

@Trudy Claspill , thank you for your response.

What would I choose as the value to use ?

[Trudy Claspill]

Oh, rats! I thought it would let you pick any User Picker custom field.

In that case, use the Smart Value option instead and for the smart value use

{{issue.your custom User Picker field name.accountId}}

[Elif Alverson]

It did not work. The assignee is "unassigned". Am I doing something wrong?

[Trudy Claspill]

You need to substitute into the smart value the actual name of your custom User Picker field.

{{issue.your custom User Picker field name.accountId}}

[Elif Alverson]

Am I missing a step?

[Trudy Claspill]

Replace only the "your custom User Picker field name"  text with the actual name of your field. The {{issue. and .accountId}} that come before and after are required parts of the smart value.

[Elif Alverson]

Same Result;

[Trudy Claspill]

Can you show the entire rule, please?

Also please show the HRBP field within an issue? I want to see the field name.

Also try using a Log action to print the content of that field into the Audit Log just before the step where you try to use it.

[Elif Alverson]

@Trudy Claspill , I removed and re-added the Custom Field and it sis working great now. Thank you so much as always.

This works when the ticket is created ,  Is it possible to make this automation also work when the "HRBR" field is changed from one user to another? Thanks again.

[Trudy Claspill]

If you use the Field Value Changed trigger and specify the HRBP field instead of the Issue Created trigger, that will trigger the rule both when the field is changed after creation and when the field is set during issue creation.

[Trudy Claspill]

I just noticed the logic you posted in the last copy of your rule:

You should not be using a Branch here. If the HRBP field is a single user picker there is no need to use a branch to get the value. And Assignee can have only one value so even if HRBP has multiple values only one of them can be inserted into the Assignee field.

[Elif Alverson]

@Trudy Claspill , I changed the automation based on your recommendation and everything works great. Thank you so much! You are awesome as always.