Automation rule which fill a custom field of the epic issue type with the project category

[v_bixhi]

Hi everyone,

We are trying to create an automation rule which fill the value of a custom field of the epic issue type with the project category of the epic.

Is it possible?

I' have tried this but it doesn't seem to work.

From the audit it goes on success but actually the field isn't valued.

Am I missing something?

Thanks for every suggestion.

Valmira

[Bill Sheboy · Accepted solution]

Hi @v_bixhi -- Welcome to the Atlassian Community!

What value are you trying to store in the Roadmap Owner field?

The smart value {{issue.project.projectCategory.name}} is the Project Category value, not a user.

Kind regards,
Bill

[v_bixhi]

Hello @Bill Sheboy 

Exactly,  we want to store the Project Category value

Any suggestions 

Thanks

Valmira

[Bill Sheboy]

What type of field is "Roadmap Owner"?  If that is a user field, you cannot store a text value from Project Category there.

[v_bixhi]

The field ''Roadmap Owner'' is not a user field, is a ''select list'' text field.

[Bill Sheboy]

In that case, I believe you would need to use advanced edit with JSON rather than the basic field edit.

The syntax for updating that type of field is shown here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field

And so you would de-select Roadmap owner from the fields to change, and instead select the More Options area to add JSON for the edit, such as this:

{
  "fields" : {
    "Roadmap Owner" : { "value" : "{{issue.project.projectCategory.name}}" }
  }
}

If that does not work, it is likely that either:

• The value on the right side (from the project category) does not exactly match a value in your list.  The fix for this is to update one of the values so they match.
• Or the name of the "Roadmap Owner" field does not match the smart value.  You can find the correct smart value for your field using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[v_bixhi]

Thanks a lot @Bill Sheboy  , it was related to this '' the value on the right side (from the project category) does not exactly match a value in your list.  The fix for this is to update one of the values so they match.'' 

I fixed this and it works.

Thanks again

Kindly regards

Valmira

[Bill Sheboy]

Awesome; I am glad to learn that helped!